[Documentation] Proguard Rules for firebase products and other plugins as needed #37839
Labels
customer: crowd
Affects or could affect many people, though not necessarily a specific customer.
P3
Issues that are less important to the Flutter project
package
flutter/packages repository. See also p: labels.
Comments
raveesh-me
changed the title
raveesh-me
changed the title
|
Is there somewhere where we can find those rules ? I've added firebase_auth (but was already using analytics, messaging, in-app) and my app doesn't compile in release mode anymore with some huge logs: Never touch the proguard conf for that project yet |
eseidelGoogle
added
t: gradle
|
Related in part to #27371 I wonder what our story is for handling proguard with plugins is? @blasten or @collinjackson might know. |
9 tasks
|
Same problem for, all was working with firebase_analytics and now with firebase_remote_config and my app doesn't compile with theses errors flutter doctor Never touch the proguard conf for that project yet too |
jmagman
added
the
tool
|
I believe the main issue is with flutter firebase plugins. I was trying to build release version with code minification and obfuscation. Setting minifyenabled false in gradle OR ignore warnings and keep all public and private classes in proguard is not an ideal solution if code minification and obfuscation is needed. When i build without firebase plugins, it works just fine. An official proguard rules for flutter firebase plugins would be nice. |
TahaTesser
added
documentation
customer: crowd
jonahwilliams
removed
t: gradle
|
It would be nice to get some movement on this. I'm running into issues where my app is unable to start in release mode because Firebase Core is unable to launch. I've traced the issue down to not having the right proguard retention rules (disabling modification allows the app to launch correctly). Here's the stacktrace for reference |
|
Closing as obsolete since the Firebase plugins are no longer part of this repository. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
flutter-triage-bot
bot
added
the
package
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Use case
In the build and release on android page,
https://flutter.dev/docs/deployment/android#step-1---configure-proguard
There are indications that we need additional proguard rules for firebase products.
In the firebase launch checklist,
https://firebase.google.com/support/guides/launch-checklist#authentication
We are told to configure proguard rules to work with auth. But clicking on the link (https://firebase.google.com/docs/auth/android/start/#proguard) produces nothing at all.
This is kind of confusing. And the warnings during minification/obfuscation of release build are also very scary as to the stability of the release builds.
Proposal
Readme of the official plugins should come with their release build instructions, that include precise guidance of if there are additional configuration like proguard needed, and exactly what those rules are, and should be updated if those rules change.
The text was updated successfully, but these errors were encountered: