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
EXC_BAD_ACCESS unhandled errors #2372
Comments
Attempt at fixing this: #2375 |
Released on |
We're seeing a bunch of these too, using 12.10.5, so I think it's still an issue. Here's the stack to allow better searching for the issue in here.
|
FWIW, 96.2% of the crashes we see with this are running iOS 17.0, with the remainder being "other" so it would at least appear to be more prevalent on the next iOS release. [Edit: The rest are on macOS 14, so it would appear to be beta-only.] |
Another similar but different one on betas:
|
Same here
Incident Identifier: 64C1410D-7542-4632-9E6D-128B8BDA05F1 Date/Time: 2023-09-12 15:04:31.0136 -0300 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Kernel Triage: Thread 0 name: Dispatch queue: com.apple.main-thread |
Unfortunately, we have those issues too. |
@andresesfm Hello, this issue is still happening even after releasing version 12.11.0. |
still happen in 12.11.0 |
My fix hasn't been merged nor released |
Could we please have someone help to get the fix merged? |
I'd appreciate that! |
@arthurgeron do you think this pr would fix this crash? its also coming on resolvePromises, but from it seems like a pending transaction Thread 0 name: |
Its coming in while the app is running, not from a react native request to get history or to purchase. It says i have 55 products and 1 is pending Apr 4 13:56:35 Richards-iPhone-3 storekitd[614] : [62AAAA6F]: Found 55 products in receipt with ID monthly_subscription |
@openpathgit Transaction might mean something else, like an unfinished or ongoing purchase. |
Hi @hyochan , this PR was closed a few months back as we had a potential fix. Since it seems there are several other reports of similar issues, I was wondering if this could be re-opened? Also it seems @arthurgeron has a proposed fix. Could you please take a look and provide some insight on what would be needed to push this through? Thanks! |
Description
EXC_BAD_ACCESS app crash. We're tracking an increase of unhandled errors since upgrading from 10.0.3 to 12.7.3.
Heres a public link to the stack trace: https://solo-6v.sentry.io/share/issue/2fda123fd6b6463e8583ae2b5076819c/
Expected Behavior
We have not been able to reproduce this issue consistently, but continue to see crash reporting on it.
Screenshots
n/a
Environment:
To Reproduce
N/a have not been able to consistently reproduce
The text was updated successfully, but these errors were encountered: