Couldn't find key stacktrace in dynamic #438
Comments
|
We have moved to another service so I close this. |
|
I am having the same problem. Could you reopen? |
|
How do I reproduce this, does this only happen when remote debugging on Android? |
|
I too have what seems to be this error on [email protected] Yes, this error only happens when remote debugging on Android and when an error is being captured. |
|
It happens only when the remote debugger is on. had to disable sentry on android while debugging, just comment the |
|
Same issue here |
|
It happends when your app crashes and your remote debugger is running. |
|
Any updates on this? |
|
Also having this problem... |
|
We're also having this problem. For now we disable Sentry while using remote debugging. |
|
I am experiencing this error in production with no remote debugging set up. It is intermittent and rare, but happens: |
|
@HazAT the fatal error that my app is trying to report doens't have a |
|
Hello, any news on this? Same thing happening here 😢 |
|
I eventually found the cause of this error for my particular case. I was directly Problem: Solution: |
|
I had the same issue. Once I turned off the That said, I would expect the Sentry SDK to be able to deal with unhandled promise rejections |
|
I have the same issue... |
|
Yeah, I'm going to have to quit using Sentry soon if this doesn't get fixed. It throws this error in production, which covers up real errors and makes them impossible to track down. Total dealbreaker. |
|
I have same issue. |
|
It seems, that Sentry cannot catch some error and crashes the app. gwmccull 's solution to figure out the error works. But it is temp solution, need fix in Sentry project code. |
|
I'm experiencing this as well. |
|
Our issue is also being caused by a non-fatal unhandled promise rejection occuring while remote debugging. With Sentry disabled I get a warning in the console, unfortunately without a stacktrace, which means I've not been able to find the specific offender and attach a catch to it (assuming it's even in our code and not in a library somewhere). Our programmatic workaround is also to disable Sentry while remote debugging. Concretely, we're defining It's unfortunate not to have Sentry working in our local dev environments, as sometimes the output can actually be better than the remote debugger. But it's obviously not worth the occasional crashes. Sentry devs, if anyone is listening, it would be really nice to have an actual fix for this issue. It's clearly bad behavior to be crashing the app in your code. |
|
I have the same issue while remote debugging. |
|
Same^ |
|
We solved this problem by disabling native integration on android in dev mode: Sentry.config(Constants.XG_SENTRY_KEY, {
deactivateStacktraceMerging: true,
disableNativeIntegration: __DEV__ === true && Platform.OS === 'android',
}).install();The impact of this is minimal and it solves the problem. The inspiration for this solution came from #6 |
|
I am closing all old issues, please if this is still a problem feel free to revive it. |
OS:
Platform:
Output of
node -v && yarn -v && yarn list --prod --depth=0Config:
I have following issue:
When I turn on
Debug JS Remotely, app crashes with error message below.Steps to reproduce:
Debug JS RemotelyActual result:
Expected result:
The text was updated successfully, but these errors were encountered: