Thread 1: EXC_BAD_ACCESS (code=1, address=0x10)

Describe the bug Thread 1: EXC_BAD_ACCESS (code=1, address=0x10) That occurs at some point during subscription receiving data.

Device.swift

private func resolve(_ key: String, _ value: String) {
        let callback = self.callbackMap[key] // Thread 1: EXC_BAD_ACCESS (code=1, address=0x10)
        ...

To Reproduce

1. Subscribe to 4 characteristics.
2. 1 Characteristic is receiving data (< 200bytes) every 100ms.
3. 1 Characteristic is receiving data (< 200bytes) every 1000ms.
4. 2 other characteristics aren’t receiving any data.

Expected behavior Expect the App not to crash when it appears to hit a null pointer in resolve().

Screenshots If applicable, add screenshots to help explain your problem.

Plugin version:

• @capacitor-community/bluetooth-le: 1.5.0

Desktop (please complete the following information):

• N/A

Smartphone (please complete the following information):

• Device: iPad Pro
• OS: iOS 15.1

Additional context

[pwespi]

Thanks for looking into this and reporting back.

I agree that with some pub/sub models, you can resubscribe without side-effects. However I see startNotifications more like something similar to WebSockets, where you would also only open one socket per app and then share that data. Rewriting startNotifcations to allow resubscribing without side-effects would be quite some effort, so not sure if it’s worth it.

I added a note to the documentation. With this I would consider this issue closed for now. Let me know if you don’t agree.

[allidoisace]

Yes, my code was running the start notification repeatedly.