-
Notifications
You must be signed in to change notification settings - Fork 1.6k
iOS 18.3.2+ Cloud Firestore could not connect to backend. #14712
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
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
This may not be the right repository for this issue. Where is the NSURLSession usage coming from? Capacitor? Wherever it is may need a similar workaround as discussed in #14677. |
@paulb777 You may be right, it seems I've been able to come up with a workaround in @ionic-team/capacitor which atleast allows Firestore to connect. |
Sounds good. I'll close for now, but feel free to reopen if you find something else. |
Description
Recently when testing our app for iPad Air (5th generation) on iOS 18.4 or iOS 18.3.2+ an issue connecting to Cloud Firestore has caused our app to not pass Apple's review stage.
I should mention, the simulator is indeed connected to Internet as I've double check many times with Safari when testing.
Initially I thought it was the Firestore configuration, it's odd for me because if I freshly install the app on the simulator device it works fine, yet say I close the app after a fresh install, or just use it normally then this error arises and causes Firestore to not connect.
For context the following is a reference to the issue at firebase-js-sdk and a reproduction repo for testing:
firebase-js-sdk Issue #8889
khaelou/bare
Reproducing the issue
No response
Firebase SDK Version
11.6.0
Xcode Version
16.3
Installation Method
N/A
Firebase Product(s)
Firestore
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetThe text was updated successfully, but these errors were encountered: