-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash when deployed to Google Play Console Internal Testing #796
Comments
One thing to also note is that on our We are also in the process of applying the TImeUse functionality to the main branch but encountered a separate issue we are vigorously looking into. So we figured we want to (re)deploy the working app (which is out of date) for the users to use. Any assistance and guidance is appreciated. Thank you so much in advance. |
The error is right there - it is missing the
|
Good morning,
We have attempted to deploy our app to Google Play Internal Testing. The branch that we are trying to deploy is not the latest with the master branch.
The code on this branch still generates the
.apk
extension in thesign_and_align_keys.sh
script, whereas the new Google standard now only accepts the.aab
extension to upload to the Play Console. Understandably there has been an update to this script file to accomodate that change.The workaround approach we took to tackle this was to borrow the above script when running the Android build hoping that the
.aab
extension will be generated instead of the.apk
.However, the change in that script alone still does not generate the
.aab
extension. The next step we tried was to "borrow" thesetup
andbin
folders from the latest code as well aspackage.cordovabuild.json
to get the latest version of cordova and then ran the build script. The.aab
extension was successfully generated as per our expectation in which we were able to upload to Google Play Console for Internal Testing.We also did refer to this issue: #680
Once deployed, we tested the app on a physical Android device but it kept crashing. When checking the logs on the Crashes and ANRs report, below screenshot of the stack trace.
Please advise if there is any step configuration step that was missed that is causing the app to crash.
The text was updated successfully, but these errors were encountered: