iOS Crash sometimes
See original GitHub issueMobile Device Environment Provide a list of operating systems on which this issue is relevant.
- Device: iPad
- OS: iOS 15
Application Environment Provide information about your development environment:
- React Native version: v0.64.1
- RN Bluetooth Classic version: v1.60.0-rc.16
Describe the bug
Sometimes after a while that I have connected the BT device, and I have sent and received data the app crashed. I think it could be a problem with memory because the device is always sending data and I see in logs that is constantly saying Stream %@ has bytes available
. But this is my simple guess.
The Bluetooth device is a LEGO Spike Prime.
The app crashed with this error and occurs in the DelimitedStringDeviceConnectionImpl.swift
file line 237
AppStoreTools: 13A227
AppVariant: 1:iPad7,11:15
Beta: YES
Code Type: ARM-64 (Native)
Role: unknown
Parent Process: launchd [1]
Coalition: es.robotix.c360 [569]
Date/Time: 2021-10-18 17:19:21.2074 -0300
Launch Time: 2021-10-18 16:12:47.2594 -0300
OS Version: iPhone OS 15.0.2 (19A404)
Release Type: User
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00004a63d2d1f290
Exception Codes: 0x0000000000000001, 0x00004a63d2d1f290
VM Region Info: 0x4a63d2d1f290 is not in any region. Bytes after previous region: 81311562855057
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated)
--->
UNUSED SPACE AT END
Exception Note: EXC_CORPSE_NOTIFY
Terminating Process: exc handler [481]
Triggered by Thread: 0
...
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x00000002802ef2a0 x1: 0x000000018883fd00 x2: 0xfffffffffffffff3 x3: 0x0000000280fe9bb3
x4: 0xfffffffffffa8e00 x5: 0x0000000000000020 x6: 0x00000002802f6990 x7: 0x0000000000000000
x8: 0x00004a63d2d1f2a0 x9: 0xfffffffe00000000 x10: 0x0000000000000001 x11: 0x0000000100000028
x12: 0x0000000000000000 x13: 0x6e22202c22626338 x14: 0x227274705f747865 x15: 0x0d7d7d323135203a
x16: 0x00000001dc89a820 x17: 0x00000001855c5914 x18: 0x0000000000000000 x19: 0x000000016b526710
x20: 0x000000016b526710 x21: 0x000000011bd34496 x22: 0x000000011bd34400 x23: 0x00000002802ef2a0
x24: 0x0000000000000000 x25: 0x0000000104c90000 x26: 0x0000000104c8b000 x27: 0x00000001f11d5000
x28: 0x00000001f11d5000 fp: 0x000000016b526660 lr: 0x0000000188265834
sp: 0x000000016b526650 pc: 0x000000018883ef28 cpsr: 0x60000000
esr: 0x92000004 (Data Abort) byte read Translation fault
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
9 Fixes for When Your iPhone Apps Keep Crashing
9 Fixes for When Your iPhone Apps Keep Crashing · 1. Check Your Internet Connection · 2. Close and Relaunch the App ·...
Read more >Fix Apple iPhone with apps that keep crashing after iOS 13
Troubleshooting Apple iPhone with apps that keep crashing after iOS 13 · First solution: Clear all background apps. · Second solution: Restart ...
Read more >My iPhone Keeps Crashing! Here's The Real Fix.
My iPhone Keeps Crashing! Here's The Real Fix. · Restart Your iPhone · Close Out Of Your Apps · Update Your iPhone Software...
Read more >This Is What to Do If Your iPhone Keeps Crashing - Mobitrix
iPhone keeps crashing? How to fix? · Method 1: Turn off the problematic application · Method 2: Clear storage and memory on your...
Read more >[Top 7 Ways] Fix iPhone Apps Keep Crashing on iOS 16
Part 2: 6 Common Ways to Fix iPhone Apps Crashing after iOS 16 Update · Way 1: Force Quit the Crashed App and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, solid work around for now. Sorry about that. Glad you’ve got something working though.
Sorry, I couldn’t do the test. Because I hurried I went with the solution of creating a timer on js side.
When I test the options that you gave me, I will let you know. Probably next week.