Bug Fixes
-
crashlytics, ios: forward port to firebase-ios-sdk v9 header locations (e5bd716)
-
storage, ios: correct storage metadata update / delete (2dcb079)
-
storage, ios: surface underlying reason for unknown errors if possible (6cd53ea)
-
test(functions, ios)!: disable custom HttpsError testing (a56dc9f)
-
fix(storage, android)!: android now updates customMetadata as a group (d602436)
BREAKING CHANGES
-
ALL iOS: firebase-ios-sdk now requires
use_frameworks!in your Podfile and Xcode 13.3+. Note that
use_frameworks is not yet compatible with Hermes, Flipper, React Native New Architecture, or react-native 0.69.0.
Each of these is being worked on (follow react-native 0.69 PR, Hermes PR) but for now you need react-native 0.68.2 or below, and you must disable hermes and flipper. Expo users should use expo-build-properties + Expo SDK45 to turn on use_frameworks in dynamic mode. -
Storage(customMetadata): android works like web+iOS now: customMetadata if passed in will be
updated as a single atomic unit, all keys at once. Any key you want to keep in customMetadata
must be passed in during update; any missing keys will be removed. Set customMetadata to null
in order to remove customMetadata entirely, omit it during update to leave it unchanged. -
Functions(custom errors): if your firebase functions return custom HttpsError instances, you must not upgrade yet,
custom errors suffered a regression in firebase-ios-sdk 9.0.0 and 9.1.0. The next firebase-ios-sdk release
fixes this regression, at which point you may safely use this release in combination with overriding the firebase-ios-sdk
version in your Podfile