-
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
Firebase auth crashes the app with: [GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance #2512
Comments
This looks similar to crashes that can be caused by missing linker flags. Can you share the stack trace of the crash? |
This is my linker flags: https://github.com/eyalevy/trustkit-firebase-sample/blob/e048d3d4ae630b3e97c814bcf2b1c42449d3a85d/ios/trustkitfirebasesample.xcodeproj/project.pbxproj#L1228 Also this is the stack trace:
|
Linker flags look fine to me. @renkelvin can you take a look? |
Hi all, I believe it's not an issue with the Auth SDK. GTMSessionFetcher is our main entry point talking to backend. All requests would fail if GTMSessionFetcher is not properly linked. Could you try other apis to see if it's the same issue? |
@eyalevy Please share the |
Sure, the links for
I want to add that this issue happened when we upgrade Firebase SDK version from version 4.9 to version 5.15. when I downgrade Firebase SDK to version 4.9 the app is not crashing. |
@renkelvin I tried to use firebase storage for getting a file and I succeed to read it. |
@renkelvin @paulb777 did any of you experience this error? |
@eyalevy I wonder, if you can reproduce the crash if you remove If we know this we may narrow down the issue search area. Thanks. |
@maksymmalyhin when I disable swizzling or remove TrustKit completely the issue doesn't reproduce. I want to add that we did not add TrustKit recently. The last change we did is to upgrade Firebase SDK from version 4.9 to version 5.15. With Firebase SDK v4.9 and TrustKit the issue doesn't reproduce as well. |
@eyalevy Thank you for the quick response. We will investigate how we can fix it. |
It looks like there is an open PR to fix the issue google/gtm-session-fetcher#130 |
It looks like the google/gtm-session-fetcher#130 creator stopped responding to the reviewer's questions months ago, so the discussion would need to be revived. |
I commented in google/gtm-session-fetcher#130. |
This should be fixed with google/gtm-session-fetcher#142. Please comment here if you run into the issue again. |
I am experiencing this issue. |
@thetminko can you share your stack trace and Firebase versions? |
@morganchen12 Thanks for replying. These are my env and logs. --- Podfile --- --- Podfile.lock ---
--- Error Logs ---
--- Stacktrace ---
|
Describe your environment
Describe the problem
the app crashes when using signInWithCustomToken. the error log is:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[GTMSessionFetcher setFetcher:forTask:]: unrecognized selector sent to instance
.It seems there is a collision beetween firebase sdk and Trustkit (https://github.com/datatheorem/TrustKit).
Steps to reproduce:
Run the example app in this repository (react native, although it does not seem related...):
https://github.com/eyalevy/trustkit-firebase-sample
The text was updated successfully, but these errors were encountered: