-
Notifications
You must be signed in to change notification settings - Fork 4k
fix(crashlytics): read firebase_crashlytics_collection_enabled from AndroidManifest.xml #13217
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
fix(crashlytics): read firebase_crashlytics_collection_enabled from AndroidManifest.xml #13217
Conversation
// if so. | ||
Logger.getLogger().e("Could not read data collection permission from manifest", e); | ||
} | ||
return null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this default to false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should default to true as stated in the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes to true sorry, then you can simplify
if (manifestEnabled != null) {
FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(manifestEnabled);
enabled = manifestEnabled;
} else {
FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true);
enabled = true;
}
to only
FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(manifestEnabled);
enabled = manifestEnabled;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. That should work.
Description
Crashylytics does not read
firebase_crashlytics_collection_enabled
meta data from AndroidManifest.xmlRelated Issues
Closes 13105
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?