-
Notifications
You must be signed in to change notification settings - Fork 34
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 reports coming from hasFeature() #84
Comments
Hi @marcshilling - thanks for raising this. Are you able to provide some more info:
|
Hey there @dabeeeenster.
For the time being we've wrapped our |
Are you able to log the response from the API that is causing the failures via the SDK somehow? @kyle-ssg are there any hooks for this? Ideally logging the JSON payload from the API? |
This is fixed as of 1.6.7 of react-native-flagsmith and flagsmith. Basically this was a super slim usecase whereby the previous analytics events hadnt been read from local storage at the point when tracking new events. |
@marcshilling Feel free to re-open this if you spot the issue after updating to this version 🙌 |
We are using
"react-native-flagsmith": "1.6.2"
in our production iOS/Android apps and we are seeing occasional crash reports coming from within your library on lines where we callflagsmith.hasFeature()
.On Android devices it comes through as:
![image](https://user-images.githubusercontent.com/5598961/132036234-b1e5d58f-bdb7-42eb-94c4-2cd13b7e050a.png)
On iOS:
![image](https://user-images.githubusercontent.com/5598961/132036172-26fc2d1a-0a6f-4e05-9d38-000d03d98f37.png)
The text was updated successfully, but these errors were encountered: