feat(firebase_core): v1 rework (#7)

[Salakar]

---

Co-authored-by: @Ehesp
Co-authored-by: @greghesp
Co-authored-by: @helenaford
Co-authored-by: @kirstywilliams
Co-authored-by: @Salakar

---

NEW DOCUMENTATION.

---

Description

As part of our on-going work for #2582 this is our finalised Firebase core rework changes.

Firebase Core changes

• DEPRECATED: FirebaseApp.configure method is now deprecated in favor of the Firebase.initializeApp method.

• DEPRECATED: FirebaseApp.allApps method is now deprecated in favor of the Firebase.apps property.

  • Previously, allApps was asynchronous & is now synchronous.

• DEPRECATED: FirebaseApp.appNamed method is now deprecated in favor of the Firebase.app method.

• BREAKING: FirebaseApp.options getter is now synchronous.

• FirebaseOptions has been reworked to better match web property names:

  • DEPRECATED: googleAppID is now deprecated in favor of appId.
  • DEPRECATED: projectID is now deprecated in favor of projectId.
  • DEPRECATED: bundleID is now deprecated in favor of bundleId.
  • DEPRECATED: clientID is now deprecated in favor of androidClientId.
  • DEPRECATED: trackingID is now deprecated in favor of trackingId.
  • DEPRECATED: gcmSenderID is now deprecated in favor of messagingSenderId.
  • Added support for authDomain.
  • Added support for trackingId.
  • Required properties are now apiKey, appId, messagingSenderId & projectId.

• NEW: Added support for deleting Firebase app instances via the delete method on FirebaseApp.

• NEW iOS: The default Firebase app is now automatically configured without needing to manually add Objective-C code to your iOS application.

• NEW: Added support for returning consistent error messages from firebase-dart plugin.

  • Any FlutterFire related errors now throw a FirebaseException.

• NEW: Added a FirebaseException class to handle all FlutterFire related errors.

  • Matching the web sdk, the exception returns a formatted "[plugin/code] message" message when thrown.

• NEW: Added support for setAutomaticDataCollectionEnabled & isAutomaticDataCollectionEnabled on a FirebaseApp instance.

• NEW: Added support for setAutomaticResourceManagementEnabled on a FirebaseApp instance.

• Android: Gradle build tools updated to 3.5.0 from 3.3.0.

• Android: Removed Gradle ‘hacks’ and upgrade Flutter SDK requirement from >=1.12.13+hotfix.4 to >=1.12.13+hotfix.5 - based on PR Remove Gradle hacks and upgrade SDK flutter/plugins#2651

• Android: Switched to using Firebase BoM to manage SDK versions

Other plugins changes

• Update e2e dev dependency to latest version on all plugins & examples.
• Fixed integration tests that were exiting with a success status even though there was failures.
• Dynamic Links example was using an API that no longer existed on the plugin - this caused a build failure when all plugins were linked together.
• Setup integration testing for Web, iOS & Android.

---

Related Issues

• CLOSES: [firebase_core] Add delete to FirebaseApp #1876
• CLOSES: [firebase_core] gradle error #335
• CLOSES: Documentation contradiction #2295
• CLOSES: Firestore add check if GoogleService-Info.plist isn't present #1229
• CLOSES: [firebase_core] for iOS will not connect to Firebase #1329
• CLOSES: [Codelab] Firebase for Flutter Codelab missing firebase_core #2261
• CLOSES: [firebase_core] v 0.4.1+5 incompatible with image_picker: ^0.6.1+11 #1437
• PARTIAL: [FlutterFire Plugins] - Lack of pattern when instanciating/getting the instance of the FlutterFire plugins #1667
• PARTIAL: [firebase_core] iOS does not compile when I add the dependency #2306
• PARTIAL: [cloud_firestore] Xcode build extremely slow #349
  • Standardising version locking from firebase_core should help build times

---

Related Pull Requests

• CLOSES: [firebase_core] Updated documentation for FirebaseOptions.apiKey #1894
• PARTIAL: [all] Switch Android from api dependencies to implementation dependencies #39

Breaking Change

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

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.