Skip to content
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 on Android - NoSuchKeyException: frames #742

Closed
4 tasks
chgsilva opened this issue Jan 21, 2020 · 7 comments · Fixed by #749
Closed
4 tasks

Crash on Android - NoSuchKeyException: frames #742

chgsilva opened this issue Jan 21, 2020 · 7 comments · Fixed by #749

Comments

@chgsilva
Copy link
Contributor

OS:

  • Windows
  • [ X] MacOS
  • Linux

Platform:

  • iOS
  • [ X] Android

SDK:

  • [X ] @sentry/react-native
  • react-native-sentry

@sentry/react-native: 1.2.1
react-native version: 0.60.5

Init Code:

    Sentry.init({
      dsn: "...@sentry.io/...",
      environment: Config.NAME,
      sampleRate: 0.7
    });

    Sentry.setTags({
      appVersion: DeviceInfo.getVersion(),
      systemVersion: DeviceInfo.getSystemVersion()
    });

I have following issue:

I started to receive this error on both Sentry and Crashlytics, I don't really know how to reproduce it, but it is occurring in +/- 1% of our users and it is really annoying. Seems like to be an issue with Sentry itself.
Anyone know how can i fix it?

Fatal Exception: com.facebook.react.bridge.NoSuchKeyException: frames
       at com.facebook.react.bridge.ReadableNativeMap.getNullableValue(ReadableNativeMap.java:124)
       at com.facebook.react.bridge.ReadableNativeMap.getNullableValue(ReadableNativeMap.java:128)
       at com.facebook.react.bridge.ReadableNativeMap.getArray(ReadableNativeMap.java:168)
       at io.sentry.RNSentryModule.sendEvent(RNSentryModule.java:320)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158)
       at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:873)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
       at android.os.Looper.loop(Looper.java:201)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
       at java.lang.Thread.run(Thread.java:764)
@olcayjotform
Copy link

We started to receive the same problem with our latest release however we didn't update the sentry library.

@sentry/react-native: 1.0.9
react-native version: 0.59.10

com.facebook.react.bridge.NoSuchKeyException: frames at com.facebook.react.bridge.ReadableNativeMap.getNullableValue(ReadableNativeMap.java:137) at com.facebook.react.bridge.ReadableNativeMap.getNullableValue(ReadableNativeMap.java:141) at com.facebook.react.bridge.ReadableNativeMap.getArray(ReadableNativeMap.java:202) at io.sentry.RNSentryModule.sendEvent(RNSentryModule.java:305) at java.lang.reflect.Method.invoke(Method.java) at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372) at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158) at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java) at android.os.Handler.handleCallback(Handler.java:873) at android.os.Handler.dispatchMessage(Handler.java:99) at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29) at android.os.Looper.loop(Looper.java:227) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232) at java.lang.Thread.run(Thread.java:764)

@michael-pr
Copy link

We are also running into this issue, same exact stack trace.

"@sentry/react-native": "1.0.6",
"react-native": "0.59.10",

@victormartingarcia
Copy link

victormartingarcia commented Jan 23, 2020

Same issue here:

"@sentry/react-native": "1.2.1",
"react-native": "0.59.10"

@eeynard
Copy link

eeynard commented Jan 23, 2020

Same here:

"@sentry/react-native": "^1.2.1",
"react-native": "0.61.5",

@victormartingarcia
Copy link

Patching @sentry/react-native v1.2.1 with the PR #743 fixes the crash. The error shows up on sentry with title <unlabeled event> and no stack trace though

@HazAT
Copy link
Member

HazAT commented Jan 27, 2020

1.2.2 is on the way, which should at least fix the crash.
Also, this PR should fix this issue once and for all #749
Closing this now.

@HazAT HazAT closed this as completed Jan 27, 2020
@vikjovanov
Copy link

Quick question to know if I need to do an emergency patch: Does this result in cutting the application completely? Or is it a background error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants