-
Notifications
You must be signed in to change notification settings - Fork 10
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
Integrating UXCam shows repetitive crashes in crashlytics #60
Comments
I apologize for the inconvenience @niranjanshk27 We will be releasing a new version of our React Native SDK that targets this specific crashes, I will keep you posted, but please let me know if you have further questions. |
@DFDIEGOH Thank you for the response. Is there any timeline for the release? If you are releasing soon, we don't have to look for alternatives, otherwise, we have an urgent delivery. |
Hi @niranjanshk27 We expect to release a new version of our SDK by the end of this week or early next week, as soon as this is out I will let you know! |
Hi @niranjanshk27 I just wanted to mention that we have release a new version of our SDK that should fix this issue, Would it be possible if you upgrade to version 5.4.1 and check if this issue has been fixed? Please let me know |
@DFDIEGOH - on 5.4.1 i see many issues in crashlytics Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.WeakReference.get()' on a null object reference main (timed waiting): tid=1 systid=28815 |
Hello @shreysaroch these have been tackled on the latest SDK version, 5.4.2. Would it be possible to upgrade and let us know if this behaviour persists or indeed it's working as expected now? Thanks |
I've done basic integration of UXCam and it started to show repetitive crashes in firebase crashlytics. Here is what the stack trace shows:
Fatal Exception: java.lang.StackOverflowError
FrescoDecodeExecutor-6
Here is a screenshot it might be helpful or might not Idk
Details:
react-native: 0.66.1
react-native-ux-cam: ^5.4.0
The text was updated successfully, but these errors were encountered: