You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using Flutter SDK version 3.16.9 along with the Firebase iOS SDK in our project. We've encountered an issue with the latest version of FlutterFire. The issue stems from a recent update in which firebase_core_web, a dependency of FlutterFire, has been modified to use the web package version 0.5.1. This specific update has made the latest FlutterFire incompatible with Flutter SDK 3.16.9, which is a significant obstacle for us.
Our primary concern arises from the recent incompatibility between the latest FlutterFire and Flutter SDK 3.16.9, which we fear may prevent us from utilizing the latest versions of the Firebase iOS SDK moving forward. This is particularly troubling because updating to a version of the Firebase iOS SDK that supports the upcoming Privacy Manifest and code signature requirements is essential for us. These updates are critical for our future releases. The current limitation poses significant challenges to our development process.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
We are currently using Flutter SDK version 3.16.9 along with the Firebase iOS SDK in our project. We've encountered an issue with the latest version of FlutterFire. The issue stems from a recent update in which firebase_core_web, a dependency of FlutterFire, has been modified to use the web package version 0.5.1. This specific update has made the latest FlutterFire incompatible with Flutter SDK 3.16.9, which is a significant obstacle for us.
web
package to 0.5.1 #12469Our primary concern arises from the recent incompatibility between the latest FlutterFire and Flutter SDK 3.16.9, which we fear may prevent us from utilizing the latest versions of the Firebase iOS SDK moving forward. This is particularly troubling because updating to a version of the Firebase iOS SDK that supports the upcoming Privacy Manifest and code signature requirements is essential for us. These updates are critical for our future releases. The current limitation poses significant challenges to our development process.
We are reaching out for advice or possible solutions on two fronts:
Any guidance or suggestions on how to navigate this situation would be greatly appreciated.
Thank you for your time and assistance.
Beta Was this translation helpful? Give feedback.
All reactions