I spent too long trying to figure out why my app with a library I was using couldn't read from the battery service only to find out it didn't have anything to do with their code but saving configurations in the Connect for Desktop BLE app.
When pre-loading config, maybe even when adding new services/characteristics, it seems you need to be very specific with the order in which you save and apply things.
Add service, save, apply, popup to confirm.
When loading config: Clear first (?), apply, popup to confirm, load setup, apply, popup to confirm.
I wasn't doing things in this exact order so I couldn't read or write. It'd be great if pressing "Apply to device" does all of that in the background.
I spent too long trying to figure out why my app with a library I was using couldn't read from the battery service only to find out it didn't have anything to do with their code but saving configurations in the Connect for Desktop BLE app.
When pre-loading config, maybe even when adding new services/characteristics, it seems you need to be very specific with the order in which you save and apply things.
I wasn't doing things in this exact order so I couldn't read or write. It'd be great if pressing "Apply to device" does all of that in the background.
Repro steps would be:
For more system details see this post: https://github.com/woodemi/quick_blue/issues/133