-
Notifications
You must be signed in to change notification settings - Fork 485
FirebaseUI / FirebaseAuth Crash on phone number validation #476
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
Can you try adding the |
@morganchen12 it's there, I'm using a lot of ObjC stuff from pods... Was checking before submitting, actually. |
Can you share your project? |
Hello @morganchen12 - want to save your eyes from bleeding, and my ass from infringement,
Meanwhile, main project configured that way:
|
Actually, I see now where's -ObjC is missing... |
Your comment seems to be missing the flags for your main app target (shows only Pod targets, unless I'm mistaken). Were you able to solve this? |
@gelosi hi, i'm having the same issue. Did you manage to fix it? Could you please provide more details? |
My issue was resolved only by moving back to FirebaseAuth 4.6.1 (version that I previously used) instead of the latest 5.0.4 atm. |
@morganchen12 @hawk-ukr hi there. I’ts a while since I’ve opened this ticket. Having crazy time now :/
|
How is this issue fixed? |
@thetminko please open a new issue with your project configuration and the crash stack trace. |
@thetminko issue is inside another dependency: google session fetcher there's approved MR solving the issue; make sure you're on the latest pods, then you should be fine; or it's something new :) https://github.com/google/gtm-session-fetcher/pull/142/files |
@gelosi I was using pod version 1.7.5. Is it because FirebaseAuth was using GTMSessionFetcher 1.1? I saw the fix is in 1.2.2. This is my env. If there is no mistake, I will log a new issue. --- Podfile.lock --- Fabric (1.10.2) 2019-08-27 10:12:59.773214+0800 PAB[19389:4469184] === TrustKit: Proxy-ing NSURLSessionDelegate: GTMSessionFetcher
|
@thetminko Yepp, try to update GTMSessionFetcher pod |
@gelosi, This is my Podfile.lock
|
well, yepp, looking at firebase's dependencies: we can tell, it's still using buggy version of fetcher ¯_(ツ)_/¯ maybe you can try cloning firebase, updating dependency and use it for yourself now, |
@gelosi Thanks and appreciate for helping. |
Welcome to FirebaseUI and thanks for submitting an issue!
✅ Please take a look at open issues, as well as resolved issues, to see if your issue is either already being addressed, or has been solved by someone else.
✅ If your issue concerns the CocoaPods error, "...transitive dependencies that include static binaries", please take a look at any of the following issues and see if your problem is solved: #48, #47, #46, #34, #23.
If not, please feel free to fill in the following info so we can help faster!
Step 1: Are you in the right place?
I'm in the right place * ✅
For issues or feature requests related to the code in this repository file a GitHub issue.
For general technical questions, post a question on StackOverflow tagged appropriately.
For general Firebase discussion, use the firebase-talk google group
For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel
Step 2: Describe your environment
Step 3: Describe the problem:
Getting a crash inside Firebase components logic. (right after typing in phone number and taping 'Verify')
I understand it can be wrong use of GTMSessionFetcher in the Firebase Auth code, but also, crash happens inside this code:
GTMSessionFetcherService fetcherDidBeginFetching:
Maybe you can suggest at least correct configuration for session fetcher to work properly?
Steps to reproduce:
💥
Observed Results:
Expected Results:
Relevant Code:
Here's how I'm using FirebaseAuth
The text was updated successfully, but these errors were encountered: