com.google.firebase:firebase-bom:30.3.1 causing "There's been an error processing your app because of an archiving issue."
See original GitHub issue[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:
- For general technical questions, post a question on StackOverflow with the firebase tag.
- For general Firebase discussion, use the firebase-talk google group.
- For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.
[REQUIRED] Step 2: Describe your environment
- Android Studio version: AS chipmunk patch 2
- Firebase Component: BOM
- Component version: 30.3.1
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
I updated firebase BOM today from
implementation(platform(“com.google.firebase:firebase-bom:30.2.0”)) to implementation(platform(“com.google.firebase:firebase-bom:30.3.1”)) and now when i try to upload to firebase app dist I get this error:
Error: failed to upload release. There's been an error processing your app because of an archiving issue. Use zipalign in your build process and try again. Learn more at https://developer.android.com/studio/command-line/zipalign If this problem continues, contact Firebase support.
Additional information about this error:
APK is not zip aligned.
Issue Analytics
- State:
- Created a year ago
- Comments:21 (4 by maintainers)
Top Results From Across the Web
Firebase Android SDK Release Notes - Google
Fixed a Firebase App Check issue that caused Cloud Firestore listeners to stop working and receive a Permission Denied error. This issue only...
Read more >android - The library com.google.firebase:firebase-iid is being ...
I had the same issue. A quick fix would be to disable the strict version checking that is causing this problem. Add
Read more >Firebase 9.0.2 Uncaught exception fatal exception
compile "com.google.firebase:firebase-database:9.0.2" ... So far this has always been due to using Firebase Database from a multi-process app.
Read more >Release Notes - Play services - Google Developers
For more information, see the Firebase Android SDK Release Notes. ... what once caused a nullness warning will now cause an error when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Marking as closed. It seems to be AGP related. There’s a workaround in the issuetracker above.
Thank you @argzdev and @vcaen
Filed: https://issuetracker.google.com/issues/241469653 I think it might make sense to see if AGP team and firebase app dist team can try to see if they can figure out what changed here.