Upgrading firebase_messaging 1 to 2
Breaking1.0.5 → 2.2.0+1Breaking3New1Changed3Fixed1
BreakingUpgrade verdict
3 breaking changes.
In plain terms
- The previous 2.2.0 release changed things in a way that breaks existing apps, but it was labeled as a minor update. This release undoes that change, which means apps that already adapted to 2.2.0 will break again. Those apps should move straight to 3.0.0, which is the same change released under the correct major version.
- This version contained a breaking change that should not have shipped in a minor update. It was undone in version 2.2.0+1.
- The plugin now uses AndroidX instead of the old Android Support Library. Apps still using the old support library must migrate to AndroidX.
Must act 3 items need code or config changes
What you must change
Breaking3
Reverts the breaking 2.2.0 update, which should have been a major version bump; this revert is itself breaking for anyone who already migrated.
Marks this release as a breaking change incorrectly published on a minor version upgrade, reverted by 2.2.0+1.
Migrates from the deprecated Android Support Library to AndroidX, requiring Android apps using the support library to migrate too.
API changes
Generated by DepDelta from published Dart source. Not mixed with prose notes.
- added:
method FirebaseMessaging.autoInitEnabled(): Future<bool> - added:
method FirebaseMessaging.deleteInstanceID(): Future<bool> - added:
method FirebaseMessaging.setAutoInitEnabled(bool enabled): Future<void>