-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Crash at grpc_endpoint_add_to_pollset_set(grpc_endpoint*, grpc_pollset_set*) + 0 #14323
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Thanks for reporting, @artem-goryaev-flex. This looks related to the grpc crash in #14018. |
Thanks for reporting @artem-goryaev-flex . Please see if the recommendations in #14018 help, and let us know. I have also reached out to the grpc team to see if they have any ideas based on the stack trace. |
This is a different issue which was fixed in grpc/grpc#36921 but the fix is only available in 1.66+ |
Thanks @HannahShiSFB . @artem-goryaev-flex , would you be able to upgrade your gRPC version (see #14342), and let us know whether that solves the issue for you? |
I have released 1.65.6-pre2 with the fix, for testing you can add the following lines to you
|
@HannahShiSFB I'm seeing this crash using Firebase SDK version 11.5.0 (SPM), which uses gRPC 1.65.1. Will there be an update made to the Firebase SDK that uses 1.66.0? |
Description
Hello, we are receiving a lot of reports for this crash in grpc via crash reporting software. I could not reproduce it myself. I wonder if you might have any leads as to why does it crash as stack trace doesn't point anywhere but grpc. Thanks.
Reproducing the issue
N/A
Firebase SDK Version
11.5
Xcode Version
16.0
Installation Method
Zip
Firebase Product(s)
Firestore, Crashlytics, Authentication, Storage, Remote Config
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
N/A
If using CocoaPods, the project's Podfile.lock
N/A
The text was updated successfully, but these errors were encountered: