Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS]: Crashed: com.facebook.react.BleClientManagerQueue EXC_BAD_ACCESS

See original GitHub issue

Expected Behavior

When I initialize new BleManager(), the app shouldn’t crash.

Current Behavior

On opening of page that initializes BleManager, the app crashes

Context

Library version: 1.1.0
Platform: iOS
React-Native Version: 0.59.4
Xcode: 11.2

The error in the title is what I get from Crashlytics for either AdHoc or Release builds. Works as expected in debug.

I have put the code below in constructor, componentDidMount, & componentWillMount and still have the same error

let bleManager = new BleManager();
bleManager.onStateChange(state => this.setState({ bleState: state, }), true);

react-native info

    System:
      OS: macOS 10.15.1
      CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
      Memory: 295.31 MB / 16.00 GB
      Shell: 5.7.1 - /bin/zsh
    Binaries:
      Node: 11.0.0 - /usr/local/bin/node
      Yarn: 1.7.0 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
      Android SDK:
        API Levels: 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 25.0.0, 25.0.2, 25.0.3, 26.0.2, 27.0.3, 28.0.3
        System Images: android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5522156
      Xcode: 11.2/11B52 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3 
      react-native: 0.59.4 => 0.59.4 
    npmGlobalPackages:
      react-native-cli: 2.0.1```

Issue Analytics

State:
Created 4 years ago
Comments:12

Top GitHub Comments

2reactions

ital0commented, Nov 11, 2019

My five cents of contribution: even if you update to Xcode 11.2.1 GM Seed, the error still occurs.

1reaction

zhaiyjgithubcommented, Nov 20, 2019

I tried this way on Xcode 11.2.1 and works: https://stackoverflow.com/questions/58595718/swift-initclassmetadataimpl-exc-bad-access-with-xcode-11-2-1

Top Results From Across the Web

[iOS]: Crashed: com.facebook.react.BleClientManagerQueue ...

When I initialize new BleManager() , the app shouldn't crash. Current Behavior. On opening of page that initializes BleManager, the app crashes ......

React Native iOS standalone crashing on react.ShadowQueue

Hi! I created an app for iOS and Android. The Android version works great, the iOS not so much. The iOS keeps crashing...

iOS14 Crash (EXC_BAD_ACCESS KERN_I…

I have tried several methods (such as using different versions of xcode build App), but still not solved... And all the people around...

iOS13 crashes instantly for some (EXC_BAD_ACCESS ...

A change in iOS 13 beta's Obj-C runtime crashes all apps that use ... in fishhook.c · Issue #25182 · facebook/react-native · GitHub...

EXC_BAD_ACCESS crash error: Understanding and solving it

EXC_BAD_ACCESS crashes are annoying but solvable using the right tools. Learn how to use the Xcode sanitizers to fix those crashes in Swift....