-
Notifications
You must be signed in to change notification settings - Fork 12
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
app crash on first start on FreeraspReactNative.onInvalidCallback() #42
Comments
Hello @nikhilborana , Kind regards, |
it crashed on both debug and release schema. only for the first time. "react-native": "0.73.4", |
Hi, yes seeing a few of these crashes on our production app on iOS only (so far). "react-native": "0.72.6", Using very simple implementation of useFreeRasp() as in docs I wasn't sure if this was related to this code in FreeraspReactNative.swift, which deliberately kills the app
Many thanks |
Hi, we found a bug that kills the app when deviceID check is fired on iOS, instead of launching your reaction. Fix will be ready later today. Thanks for bringing this up. |
You're welcome!! |
Just released v3.6.1 which should fix the problem. |
sorry to bother you guys, but now its giving Device Id not ok for the first time open and if I kill the app and reopen it is working fine. |
Hi @nikhilborana, The deviceID can be triggered after app reinstallation if none other app from the same vendor is installed on the device. So if you are reinstalling the only app installed from you, it is expected that deviceID is triggered. If you don't mind whether app was reinstalled, then it is usually fine to ignore this callback. |
getting the crash on first time open only. Install this build from testflight.
Working fine on development.
The text was updated successfully, but these errors were encountered: