-
Notifications
You must be signed in to change notification settings - Fork 4k
🐛 [Firebase_analytics] Android build has missing google_app_id after Flutter 3.0.0 upgrade #8767
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
Comments
Thanks for the report @lloydrichards. Considering the error you are getting https://github.com/firebase/flutterfire/pull/8167/files So I am guessing you are probably hitting #8098 Let us know if above links helps. If not, we can make this a documentation issue for below scenario you mentioned:
|
From looking at all the other reports, it seems like it's just the same
issue as before with no changes. I understand that analytics was marked
with a `?` before to indicate it not being fully supported on Android, but
last I saw the plugin table it looked like everything had a tick on it.
If nothing has changed since before Google IO then it must be a
documentation/marketing issue as I was very much convinced after everything
i read and saw at IO that stable releases for flutter fire meant that
something had been updated.
Maybe there's a good place to let Google/Flutter know that there are some
mixed messages?
…On Wed, 25 May 2022, 12:38 darshankawar, ***@***.***> wrote:
Thanks for the report @lloydrichards <https://github.com/lloydrichards>.
Considering the error you are getting Missing google_app_id. Firebase
Analytics disabled., this probably indicates the dart-initialization may
not yet support firebase_analytics for Android because there have been
similar reports like below:
#8098 <#8098>
#7972 <#7972>
#7866 <#7866>
#7639 <#7639>
https://github.com/firebase/flutterfire/pull/8167/files
So I am guessing you are probably hitting #8098
<#8098>
Let us know if above links helps. If not, we can make this a documentation
issue for below scenario you mentioned:
There is no clear guide on how to move from Flutter 2.10.0 /
firebase_analytics: ^9.1.2 to Flutter 3.0.1 / firebase_analytics: ^9.1.8 so
my first attempt was to remove parts of the Manual integration that were
specified in the FutterFire docs before the update to official Firebase
docs. I removed the google-service.json and the plugins for analytics,
resulting in a dlopen failed: library "libflutter.so" not found error
when building. After some StackOverflow I got the app building but now it
would show E/FA ( 8840): Missing google_app_id. Firebase Analytics
disabled. See https://goo.gl/NAOOOI whenever a Analytic event would be
normally sent.
—
Reply to this email directly, view it on GitHub
<#8767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOHWIQNMPTP6PPADNQ4JDCLVLX7LXANCNFSM5WZKZTNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The only way i have been able to make analytics work for now and stop receiving the Is there a better workaround for this issue? |
In fact it turned out to not be a viable workaround, adding the string value made me start receiving events in the Firebase Analytics DebugView but the app became irresponsive not being able to show the home screen... |
Same here, it appears like the new docs fail to mention the fact that |
If dart-only initialization does not work, what is the other way to make it work? any help on this would be appreciated. Thanks in advance. |
Hi @lloydrichards, we no longer recommend removing the I am sorry that the documentation wasn't clear, we did migrate from the archived documentation to the The problem with dart only initialization is that it was causing some issues with some plugins. As we don't have control over the native Firebase SDKs and their use of the service files, we felt it was safer to write the files to ensure the plugins behaved as intended. Hope this helps. TL;DR run |
Bug report
Describe the bug
I was really excited after Google IO to implement Flutter 3.0.0 and all the stable FlutterFire plugins but I have to say that these past two weeks have been a bit of a nightmare in confusing/out-of-date documentation and a complete lack of migration guides. My current problem/bug is that when I upgrade Firebase Analytics to just use FlutterFire I get a message during the Android build that it is missing the google_app_id and disables Analytics.
There is no clear guide on how to move from Flutter 2.10.0 / firebase_analytics: ^9.1.2 to Flutter 3.0.1 / firebase_analytics: ^9.1.8 so my first attempt was to remove parts of the Manual integration that were specified in the FutterFire docs before the update to official Firebase docs. I removed the google-service.json and the plugins for analytics, resulting in a
dlopen failed: library "libflutter.so" not found
error when building. After some StackOverflow I got the app building but now it would showE/FA ( 8840): Missing google_app_id. Firebase Analytics disabled. See https://goo.gl/NAOOOI
whenever a Analytic event would be normally sent.I have since got it the work by re adding all the instruction from the Android getting started page link but as far as I'm reading the Flutter section, this is not the intended behaviour or DX ?
Steps to reproduce
Steps to reproduce the behavior:
dlopen failed: library "libflutter.so" not found
E/FA ( 8840): Missing google_app_id. Firebase Analytics disabled. See https://goo.gl/NAOOOI
Expected behavior
When the official blog post says how things now have
drastically reduced the number of steps it takes to get started, no longer requiring you to open any platform-specific IDEs
, you feel a little cheated when you have to spend a whole day sorting this out with your dev team.Additional context
E/FA ( 8840): Missing google_app_id. Firebase Analytics disabled. See https://goo.gl/NAOOOI
Add any other context about the problem here.
Flutter doctor
flutter doctor
Flutter dependencies
flutter pub deps -- --style=compact
The text was updated successfully, but these errors were encountered: