flutterfire_ignore_scripts is null and crashes

[sgehrman]

Yeah, still happens in every one of my projects using firebase_core.

I'm on web if that matters. Reported this a while ago, never got back because I thought it was obvious.

Since there haven't been any recent updates here, I am going to close this issue.

@sgehrman if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

Originally posted by @google-oss-bot in https://github.com/firebase/flutterfire/issues/7701#issuecomment-1014070117

[sgehrman]

turn on 'All Exceptions' and 'Uncaught Exceptions' in the vscode debugger.

[darshankawar]

Could it be related to the other error you reported ? https://github.com/firebase/flutterfire/issues/9256, because it seems the reported method is called inside _initializeCore():

https://github.com/firebase/flutterfire/blob/c2771a425bd7260b11970e9e9e77ef40a39f9f16/packages/firebase_core/firebase_core_web/lib/src/firebase_core_web.dart#L107

But since you are not able to initialize it as mentioned in other issue, this exception could be triggering.

Please check this and see if after successfully initializing the Firebase app, if you still get the same error or not.

[SKnoedler]

@Lyokone

I am having the same problem and I added the proper config as shown by Lyokone. The issue does not appear if I run "flutter run --verbose" or if build the entire web application first. If I run "flutter run" oder "Run Without Debugging" or "Start Debugging" it fails initializing firebase. I am very confused. What does the verbose mode change?

Moreover, I realized the issue does not appear if I override the name within the following lines of code:

App app([String? name]) { return App.getInstance( name != null ? firebase_interop.getApp(name) : firebase_interop.getApp(), ); }

The name seems to be "[DEFAULT]" even though I specified the app name in await Firebase.initializeApp(. If I override the name with the app project name from firebase, everything works as expected.

[google-oss-bot]

Hey @sgehrman. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[Lyokone]

Hello @SKnoedler Could you create a full reproduction so I can take a look?

[google-oss-bot]

Hey @sgehrman. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@sgehrman if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.