-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 in App Check token fetch with force refresh #8544
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
@mikehardy Thank you for the report. Based on the provided stack trace it looks like the crash happens in Firebase Database. Could you please confirm that you are using Firebase Database in your app? |
Hi @maksymmalyhin ! I'm a maintainer of react-native-firebase, and we're the sanctioned bridge between the native SDKs and the react-native ecosystem, so our e2e test harness uses - to my best estimate - something like 98% of the entire API surface area of the full SDK :-) https://github.com/invertase/react-native-firebase/runs/3355573480?check_suite_focus=true#step:21:11 On iOS specifically we are not just using the database module, but we are using it against the emulator: https://github.com/invertase/react-native-firebase/blob/af336a3310d2653fe70879cd0729fba3469b15de/tests/app.js#L48-L52 - though removing that line and hitting the cloud is possible / okay to do / but untested for this issue, not sure if it has the same problem. You may see our full install set here https://github.com/invertase/react-native-firebase/blob/master/tests/ios/Podfile.lock - that's not a perma-link so versions will change shortly as I adopt 8.6.0 over in our repo but it's reasonably correct for triage here I believe. Let me know if there's anything else you need to reproduce - I know frequently the reproduction is the hardest part.... |
Thank you for the provided information. I may adjust the issue title to be more precise. I can see the reason of the issue. It is an unfortunate typo and lack of solid tests in this code section. We will provide a fix. |
Step 0: Are you in the right place?
file a Github issue.
with the
firebase
tag.google group.
of the above categories, reach out to
Firebase Support.
this repository, please delete this section.
[REQUIRED] Step 1: Describe your environment
CocoaPods
(select one)[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Send
YES
for "forceRefresh" argument in this method(DLog is just a wrapper for standard logging, use what you need)
Relevant Code:
No crash if you send
NO
in thereThe text was updated successfully, but these errors were encountered: