-
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
EXC_BAD_ACCESS (code=1, address=0x4) in AuthBackendRPCImplementation.callInternal(with:) #13480
Comments
I have been unable to reproduce it, but I am finding recent concurrency related crashes with the same It may be a Xcode 16b5 regression: |
Sounds reasonable. Should we keep an eye on it and review once Xcode 16b6 rolls out? |
@peterfriese, I think so. I'm not sure why I couldn't reproduce it though. I was using Xcode 16b5 on a physical device running iOS 17.X (I also tried the simulator). If you're able to reliably reproduce it, could you please check the other threads to see if that same class is being called elsewhere? If it's not a Xcode bug, then it may be a concurrency bug within the SDK. |
I have a prototype fix working - converting some internal methods to |
Hey! The same issue, using Xcode 16.0 beta 6 and Firebase 11.1.0. Should it be fixed in this version? |
Just got the same crash reported in prod, seems it's after I've updated Firebase to v11.2 ad GoogleSignIn 8.0.0. Crashed: com.apple.root.user-initiated-qos.cooperative |
Hi @nataliakozlovska, no, the fix was released in Firebase 11.2.0. Thanks for reporting, @ondrejkorol. Are you able to provide a full stack trace? |
Hi @ncooke3 , thanks for your quick response! I'll be happy to help, Crashlytics reports this:
Full stack trace: Data: |
Thanks @ondrejkorol! I was not able to reproduce via Xcode 15.2 (simulator/device) and Xcode 16.0 RC (simulator). I will look into if Xcode 15.4 makes a difference. From the stack trace, this looks like a slightly different issue from the original issue in this thread, especially as you are using 11.2. Could you please open a new issue using some of the info you have already provided here? Could you also please include whether you can repro this locally? https://github.com/firebase/firebase-ios-sdk/issues/new?assignees=&labels=&projects=&template=BUG_REPORT.yml |
Thank you so much! I haven't encountered this issue locally. Just got 2 reports via Crashlytics from our users. I will open the new issue with the current stack trace. |
If possible, could you also share the second crash report in that new issue? I'm wondering if the threading layout matches the first report.
Possibly, but I'm not sure so I can't give a strong recommendation. Did you previously release your app with Firebase 11.1.0? If so and it was successful, downgrading could be an option. This could also indicate that the Xcode 16 fix in 11.2 may have introduced a behavior change for apps built with Xcode 15. |
I appreciate your help! Thanks. Here's the second stack trace I got today: |
Description
When refreshing the access token, the app crashes.
Reproducing the issue
This happens shortly after launching the app and the access token is expired.
On Xcode 16.0 beta 4, this doesn't happen.
I also made tried to use the head of the
main
branch, to make sure I benefit from #13472 - but this didn't seem to have any positive impact.Firebase SDK Version
11.0.0
Xcode Version
16.0 beta 5
Installation Method
Swift Package Manager
Firebase Product(s)
Authentication
Targeted Platforms
iOS
Relevant Log Output
Using the emulator: NO WARNING: All log messages before absl::InitializeLog() is called are written to STDERR I0000 00:00:1723453304.319128 7924252 config.cc:230] gRPC experiments enabled: call_status_override_on_cancellation, http2_stats_fix, monitoring_experiment, pick_first_new, trace_record_callops, work_serializer_clears_time_cache
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetIf using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: