Skip to content

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

Merged

Conversation

SelaseKay
Copy link
Contributor

@SelaseKay SelaseKay commented Aug 25, 2024

Description

Crashylytics does not read firebase_crashlytics_collection_enabled meta data from AndroidManifest.xml

Related 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.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@SelaseKay SelaseKay requested a review from Lyokone August 26, 2024 07:17
// if so.
Logger.getLogger().e("Could not read data collection permission from manifest", e);
}
return null;
Copy link
Contributor

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?

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 think it should default to true as stated in the docs.

Copy link
Contributor

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;

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. That should work.

@Lyokone Lyokone merged commit fa8d320 into firebase:main Aug 27, 2024
17 of 21 checks passed
@firebase firebase locked and limited conversation to collaborators Sep 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants