-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[🐛] Bug - 'headerValue()' is unavailable in Swift: Use asyncHeaderValue() async -> String?
instead.
#8073
Comments
Same issue here, happening when building on EAS server's but not locally |
Are you able to reproduce the bug with my build issue reproducer here? https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh just need to plop a google services json/plist file in there and bump the RNFB version to 21.1.0 (though, I've been using firebase-ios-sdk 11.3.0 forever already and it worked...) I suspect something going on with caching or something, or perhaps the firebase-ios-sdk version is overriden in the Podfile or something? Because I haven't had any build problems like this either here in the e2e test suite app or my build reproducer 🤔 |
Same errors here in class AuthBackend |
@mikehardy |
I think it's because 11.4.0 came out and we're getting a mix of dependencies - thanks @PavelShev for posting that - very instructive workaround - pin firebase-ios-sdk in Podfile to 11.4.0 like so: https://rnfirebase.io/#ios I'm not sure if you can do that in Expo. Looks like we need a release here that can either pin the versions to "same or lower than" firebase-ios-sdk instead of letting them drift since it appears they aren't semantic versioning-safe, or to update to 11.4.0 |
For a managed Expo app I made a temp plugin to solve this:
|
I've got a PR in CI right now in #8074 that contrains the transitive dependencies a lot more tightly I will also be pursuing the actual firebase-ios-sdk update as a separate item but this should get people building again assuming CI here goes green and I can hit the merge + publish buttons |
@DiazIgnacio this is actually a pretty useful plugin in general, as there is no other way I'm aware of to set the Firebase SDK version in Expo since it is direct in the Podfile - thanks for posting that |
v21.1.1 is out with transitive dependencies contained enough that it should work for react-native-firebase folks https://github.com/invertase/react-native-firebase/blob/main/CHANGELOG.md#2111-2024-10-22 If you have added a version pin, you should probably take it out as soon as possible - it is easy to forget those and they turn into landmines in the future @maximmai I'm afraid I can't help as this is not the correct repository for that, although I will mention it internally to the Invertase crew as they should be able to have an effect on the flutter plugins. If there is a way to pin your firebase-ios-sdk dependency in the flutter firebase plugins then pinning it to 11.4.0 should fix things for you - but I don't know if there is a mechanism to do so or not - it looks like there might be but I haven't tested it |
@mikehardy |
react-native-firebase with firebase-ios-sdk 11.4.0 is out as well so this should go away for everyone for two reasons:
|
Thanks, @mikehardy! FYI, FirebaseCoreExtension 11.4.1 was published this morning to revert the problematic change. Folks on older Firebase versions that run |
Good day, I have an error after the last pod update, specifically:
'headerValue()' is unavailable in Swift: Use 'asyncHeaderValue() async -> String?' instead.
This occurs in the file AuthBackend.swift.
I am attaching screenshots:
Also, here is my package.json:
The text was updated successfully, but these errors were encountered: