EXC_BAD_ACCESS folly::Expected<long long, folly::ConversionCode> #328
Comments
|
Hey, thank you for reporting. |
|
Thanks @HazAT, this has become a daily routine and I really don't have anyway to reproduce this. |
|
I had a look at the logs, since I keep seeing more events like this. It seems to be iOS 11+ only, I have included a Stacktrace below. I am not sure if this is a sentry issue at this point. I have seen there are other people facing this issue with realm-js, code-push and sentry. However, we only use the latter. |
|
I am trying to figure out if this is related with AsyncStorage and has nothing to do with sentry. If you guys know more, please let me know. :) |
|
Hey, @edo1493! Unfortunately, we're also dealing with the same problem. Were you able to identify a fix for this? |
|
So my guess is that this is a react-native crash and only with Sentry you are able to see it ¯\_(ツ)_/¯ |
|
That's something that I'm also trying to figure out, @HazAT! The strange thing here is that these exceptions started to be thrown (not only on Sentry but also on iTunes Connect dashboard) after an update where we replaced I'll try to revert this change to check if we can get rid of new exceptions. |
|
@diegocouto hmm well, this is a very strong indication that this crash comes from react-native itself because in |
|
I keep seeing this every day, so it might be something on my side, which I haven't still figured out. |
|
Are we saying that this is a bug on our side that only react-native-sentry can catch cause raven-js doesn't read native? Or that react-native-sentry introduces the bug. 😓 The other thing is that it's iOS11 only. |
|
Thanks, @HazAT! I think you're right and the error was on our side. An update with a fix on our app went out yesterday and so far, so good. @edo1493, We were experiencing the exact same thing. The same exception, iOS11 only and we started noticing it after we've migrated to react-native-sentry. There weren't many issues on our iTunes connect before this change, so I was inclined to believe that it was something with this package BUT, changing to react-native-sentry wasn't our only change! Before sending an exception to Sentry we've added a |
|
Same error here |
|
Exactly the same as @amazinmoe here.. |
|
@amazinmoe @diegocouto @edo1493 have your issues been resolved? My app is throwing the same thing on react-native-sentry Thanks |
|
folly::Expected<long long, folly::ConversionCode> folly::detail::str_to_integral |
|
react-native-sentry: 0.35.3
and
|
|
Any updates on this? I'm seeing a lot of these issues as well. |
|
So I still expect that Sentry is not the reason for this to occur, Sentry only shows you the crash. I will leave this issue open since this seems to be rather common, just so people find this more easily. |
|
Oh. Thanks for the clarification, @HazAT :) |
|
I'm seeing something that seems pretty similar to this. It can be reproduced consistently until Sentry is disabled (at which point no more error) - but it only happens on an iPhone X (real device, not simulator). Relevant stacktrace in Sentry: Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: BUS_NOOP at 0x5000000000000000
Crashed Thread: 24
Application Specific Information:
Attempted to dereference garbage pointer 0x5000000000000000.
Originated at or in a subcall of folly::Expected<long long, folly::ConversionCode> folly::detail::str_to_integral<long long>(folly::Range<char const*>*)
Thread 24 Crashed:
0 libobjc.A.dylib 0x302a757ec objc_object::release()
1 CoreFoundation 0x3045e4df8 [inlined] cow_cleanup
2 CoreFoundation 0x3045e4df8 cow_cleanup
3 CoreFoundation 0x3045d539c _cow_release
4 CoreFoundation 0x304477480 -[__NSDictionaryM dealloc]
5 App 0x2023e25bc folly::Expected<long long, folly::ConversionCode> folly::detail::str_to_integral<long long>(folly::Range<char const*>*)Relevant stacktrace in Crashlytics: |
|
@jcicale Please try to disable stack trace merging: |
|
@HazAT we were seeing |
|
@HazAT as per the docs and changelog, If we're using a version >= 0.27.0, how would explicitly setting |
|
@phillbaker good question, will take a look. |
|
@phillbaker Just tried it and it is disabled by default, so not really sure what went wrong for you. Also, I will close this issue for now, please disable stack trace merging if you are running into this Edit: If you are running a version after |
|
@lefloh just curious, what version of react-native-sentry are you running? Did setting |
|
@phillbaker we're currently on 0.36.0. We started with 0.11.8. I'm not sure what the default was back then but we've set |
|
@HazAT since |
|
@M-Jas You don't have to if you run on the latest version. |
|
I am experiencing this issue with My configuration looks like this: import { SENTRY_DSN } from 'react-native-dotenv'
import { Sentry } from 'react-native-sentry'
import VersionNumber from 'react-native-version-number'
if (SENTRY_DSN) {
Sentry.config(SENTRY_DSN, {
// prettier-ignore
release: `${VersionNumber.bundleIdentifier}_${VersionNumber.appVersion}_${VersionNumber.buildVersion}`
}).install()
}@HazAT It does not seem like the new default value resolved the issue. @edo1493 Could you please reopen this issue, since it does not seem to be resolved yet? |
|
I am facing the same issue here, @HazAT @edo1493 : and also I got this error: Real Device throwing the error: iPhone Model: Versions: react-native: Sentry install code: Is there a way to avoid this issue? :/ |
|
@HazAT We are running the most recent, but still an issue. In fact seems like it happening more and more. |
|
I received a similar issue report today: EXC_BAD_ACCESS sentry-react-native: 0.35.3 I found a similar issue in react-native: facebook/react-native#12159 but it's closed. |
|
Any updates on this issue ? |
|
Any updates on this? |
|
Having the same problem. "react-native-sentry": "0.39.0" Stack trace doesn't really have a useful thread context |
|
Anyone have an update on this? |
|
Same here! |
|
Also getting this regularly on my test device:
|
@hugomosh I'm seeing the same error in production, with a call-stack matching #244 (while there are a few different ones listed in this issue), but using bugsnag instead of Sentry. Has anyone seen this on react-native 0.58? In particular, |
|
I received a few errors similar to this issue with RN 0.57.2, all of them have |
|
If any one gets this errors and have a image-cache. The outdated react-native-fetch-blob could be the problem |
and others
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0Config:
I get this error in production, both on iOS and Android. I have seen people reporting this in the past. I don't have anyway to reproduce this, it just shows up from time to time. I am using 0.31.0.
The text was updated successfully, but these errors were encountered: