-
Notifications
You must be signed in to change notification settings - Fork 47
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
Overview for SDK version and corresponding package versions range #66
Comments
Hey there 👋 - this does not contain quite enough details to help https://stackoverflow.com/help/how-to-ask Additionally, why wouldn't you want to use current versions (that is, 10.1.0?) You mention I think you want to add a variable to your Podfile. that defines the version that you want and all of FlutterFire will use it: 10.1.0 should work, assuming you are on the most up to date versions of your FlutterFire dependencies |
Hi Mike,
And i've checked that i'm using the most recent Firebase package versions in my pubspec.yaml. |
The Podfile is the important part, did you put: $FirebaseSDKVersion = '10.1.0' in your Podfile? Because right now firebase_core is still not picking it up, it's trying to use 10.0.0 leading to inevitable conflict. |
I name the SDK version here in my Podfile (which worked fine for e.g. version 9.3.0):
I've never seen the variable you mentioned above. Is this one required from version 10 on? |
I link-quoted the code above that uses the variable and incidentally shows how it is used. But that's your explicit goal, to manually ingest firebase-ios-sdk 10.1.0, so I'm showing you how to get what you want. How did it go when you tried it? |
It actually works, i.e. build and deployment run fine now with the most recent versions. |
Fantastic! Glad that worked - remember to remove it later when you have the version you want, so you are not forever responsible for updating it. The release of the next version this PR will be your clue that you may safely remove it firebase/flutterfire#9869 |
Does it matter if that line just stays there? |
Yes it matters how long it stays there, it should be considered "for emergency use only" as you are now responsible for all compatibility issues between firebase-ios-sdk and flutterfire modules. I'm not sure I personally would sign up for that responsibility long term. But every project is different. But if you never update it, and you leave it there, you will eventually have a compile failure. You will decide for yourself how long to leave it there and if that is important for your project. |
Ah, so this means declaring the variable FirebaseSDKVersion explicitely was only a quickfix and will be obsolete once the mentioned PR has been merged, i.e. after that action i'm good to go with "only" using
in target Runner again? |
My previous comments have answered your question |
I would like to update from SDK version 9.3.0 to 9.6.0, but i don't know (up to) which Firebase package versions i may enter in my pubspec.yaml in order that the ios build, deploy and run works fine.
Is there an overview which SDK versions correspond to the published Firebase package version ranges?
E.g. when i tried to build with version 9.6.0 i got lots of errors since the package versions of the several Firebase plugins i entered in pubspec.yaml seem to be too new.
Sorry for the dumb question, perhaps i'm completely wrong here, then just correct me. Thank you.
The text was updated successfully, but these errors were encountered: