Hello,
After installing plugins that interact with the phone’s native functions, I created a new Android build, and now the app starts but encounters an error and immediately closes.
Here’s the sequence of operations I performed:
- I had a native configuration named “Staging,” which I renamed to “Production.”
- I updated the live update channel in Visual Studio Code to “Production.”
- I generated a new build from the latest commit.
The build runs without any errors.
What could I have done wrong?
With the same configuration, the build created for iOS and sent to TestFlight is working.
You’re missing a lot of information to let anyone help you. Review: How do I ask a good question? - Help Center - Stack Overflow
I’m sorry, but I don’t have any errors to show, except for this strange behavior of the app once it’s installed.
Can I provide the project specifications if it can be of help:
“@ionic/angular”: “^7.1.1”,
“@capacitor/camera”: “^5.0.3”,
“@capacitor/core”: “5.0.3”,
“@capacitor/device”: “5.0.2”,
“@capacitor/filesystem”: “^5.0.2”,
“@capacitor/geolocation”: “^5.0.6”,
“@capacitor/google-maps”: “^5.3.2”,
“@capacitor/haptics”: “^5.0.2”,
“@capacitor/ios”: “5.0.3”,
“@capacitor/keyboard”: “5.0.2”,
“@capacitor/network”: “^5.0.2”,
“@capacitor/preferences”: “5.0.2”,
“@capacitor/status-bar”: “5.0.2”,
“@capawesome/capacitor-file-picker”: “^5.1.0”
The AppFlow build is completed, and I have the APK to install. Once installed, it experiences what I described at the beginning. The previously installed native build on the device works.
Could it be some installed plugin?
Is it recommended to delete the Android folder and add Android again?
Thanks to anyone who can help me.
Yes
It would not remove the error until you review all of your plugins.
1 Like
Okay,
by uninstalling all the plugins added since the last working build, the APK now works again. Thank you.
1 Like
