Repository navigation
Closed
Description
App crash everytime once started. Using 2.0.4 and react native pluggin
var Raven = require('raven-js');
require('raven-js/plugins/react-native')(Raven);
Raven
.config('https://https://xxx@app.getsentry.com/xxxx', { release: RELEASE_ID })
.install();
01-12 09:24:15.371 19126-19167/com.rnmenu E/ReactNative: Got JS Exception: TypeError: undefined is not a function (evaluating 'this._handleStackInfo(n,t)')
01-12 09:24:15.371 19126-19167/com.rnmenu W/dalvikvm: threadid=19: thread exiting with uncaught exception (group=0xa4d34b20)
01-12 09:24:15.411 19126-19167/com.rnmenu E/AndroidRuntime: FATAL EXCEPTION: mqt_js
Process: com.rnmenu, PID: 19126
com.facebook.react.bridge.JSExecutionException: TypeError: undefined is not a function (evaluating 'this._handleStackInfo(n,t)') (line 19 in the generated bundle)
at com.facebook.react.bridge.ReactBridge.loadScriptFromAssets(Native Method)
at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:32)
at com.facebook.react.bridge.CatalystInstance$2.run(CatalystInstance.java:138)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
at android.os.Looper.loop(Looper.java:136)
at com.facebook.react.bridge.queue.MessageQueueThread$1.run(MessageQueueThread.java:137)
at java.lang.Thread.run(Thread.java:841)
Metadata
Metadata
Assignees
Labels
No labels
Activity
Fix bad `this` value in React native plugin (fixes #468)
Merge pull request #469 from getsentry/GH-468
Fix bad `this` value in React native plugin (fixes #468)
qbig commentedon Jan 14, 2016
Hi @benvinegar . Thanks for the super prompt update. The crashing is fixed :) But as I was not receiving any event, I added an "throw new Error('test')", just to verify that sentry is properly setup. But I wasn't getting any event still. The following is the error log.
benvinegar commentedon Jan 14, 2016
@qbig – I notice this is when running on Android. Do you get the same exception from the iOS simulator / iOS devices?
benvinegar commentedon Jan 18, 2016
@qbig – any news on this?
qbig commentedon Jan 21, 2016
@benvinegar I have tried on iOS simulator. It wasn't throwing the same exception.
But I wasn't getting any events either.ok. I could get event now. Would try on android again. Let you know how it goes.With RN0.18, it's not crashing anymore. So maybe can close this issueqbig commentedon Jan 29, 2016
I was testing with Android emulator(Genymotion), and I have limit the length of the stacktrace to 1000 characters. But it only works on dev Mode. Once I build it to a release version apk, JS error would simply crash the App and no msg would be logged to Sentry.
I suspect this is caused by the different behaviours of
defaultHandler.apply(this, arguments)in dev and prod mode and the app crashed before any stacktrace was sent to Sentrynevir commentedon Feb 24, 2016
React Native's default behavior (on iOS) for global exceptions is to re-throw the exception in Obj-C land, causing an immediate crash (and no chance for Raven to upload the exception)
benvinegar commentedon Mar 23, 2017
Sentry now has a first-class React Native plugin that combines both JavaScript and native (iOS) frames in stack traces.
Closing this issue.
nevir commentedon Mar 23, 2017
feat(component-annotate): Introduce new plugin to annotate frontend c…