Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Flutterfire apps no longer show a confusing log message about configuring default app #1192

Merged
merged 19 commits into from
Feb 21, 2019

Conversation

collinjackson
Copy link
Contributor

@collinjackson collinjackson commented Feb 11, 2019

Fixes flutter/flutter#16534

Note that this doesn't completely fix the issue, it just changes the error message from the previous, really confusing:

"4.8.1 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured.
Add `[FIRApp configure];` (`FirebaseApp.configure()` in Swift) to your application
initialization.

New log message:

[Firebase/Core][I-COR000004] App with name __FIRAPP_DEFAULT does not exist.

@@ -1,3 +1,7 @@
## 0.9.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is no public api change, the version should only be updated as a patch, so 0.9.0+2
https://www.dartlang.org/tools/pub/versioning#semantic-versions
Same for everything related in this PR.
@collinjackson @mklim can you confirm?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, this is more of a bugfix and should just be bumping the patch numbers everywhere. Sometimes it is appropriate to increment the minor version just based on the behavior of private code but I don't think this change really fits that edge case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with doing this as 0.9.0+2

@collinjackson
Copy link
Contributor Author

I switched to using patch versions, will land this once the bots are happy

@Hixie
Copy link
Contributor

Hixie commented Feb 13, 2019

test?

@@ -1,3 +1,7 @@
## 0.9.0+2
Copy link
Contributor

@bparrishMines bparrishMines Feb 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't the pubspec.yaml need the version bump too?

@@ -1,3 +1,7 @@
## 0.2.0+2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pubspec.yaml version

@@ -4,7 +4,8 @@ description: Flutter plugin for Google Performance Monitoring for Firebase, an a
iOS.
author: Flutter Team <flutter-dev@googlegroups.com>
homepage: https://github.com/flutter/plugins/tree/master/packages/firebase_performance
version: 0.1.0+2
version: 0.1.0+3
>>>>>>> 4f024c7404c01e1f3b55be61704d2deb53f6ca41
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge line

@collinjackson
Copy link
Contributor Author

test?

I don't think that our current infrastructure can test this change, because the only observable impact is in the iOS device logs.

@collinjackson collinjackson merged commit 7e22fb8 into flutter:master Feb 21, 2019
@collinjackson collinjackson deleted the bugpile_defaultapp branch February 21, 2019 21:46
idealopamp pushed a commit to idealopamp/plugins that referenced this pull request Feb 21, 2019
julianscheel pushed a commit to jusst-engineering/plugins that referenced this pull request Mar 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove spurious "default app not configured" warning from Flutterfire iOS logs
7 participants