Leo Huang

Thanks for your quick reply! I set the log level before creating the Ble client like so: ``` _bleManager = BleManager(); _bleManager.setLogLevel(LogLevel.verbose); _bleManager.createClient() .then((_) => _setupBleScan()); ``` I'm not seeing...

Thank you @mikolak and @trixidis! I knew I was doing something wrong :) ` 2020-05-21 09:53:29.235201+1000 Runner[975:644992] [CoreBluetooth] WARNING: Characteristic does not specify the "Write Without Response" property - ignoring...

(Feel free to close this issue now - unless you want to use it to track work on making warnings like these more visible)

Sorry for the late reply - I tried editing my local copy (forgot you could do that!) and I can confirm that after removing the `.broadcast` I now reliably observe...

@dariuszseweryn due to the way that my app is structured, and the nature of the ble devices that I'm interacting with, I often need to temporarily monitor and then stop...

@dariuszseweryn sorry, that part was largely guesswork on my part - I haven't actually dived deep enough to verify that the exact problem is monitoring an already-monitored characteristic. The error...

@mikolak Hi, I'm just coming back to look at this again. The fix for this issue is quite simple (move to a single-subscription stream), and the reason why it hasn't...

+1 on this. We deploy our Remix server to AWS ECS, but we specifically deploy the built frontend assets to S3 + Cloudfront for better performance in serving the frontend...

I've raised a simple PR to fix this: https://github.com/opnsense/plugins/pull/3928 It renders the error instead of trying to render the result.

+1 exact same error - also slightly concerned about the lack of retry limit Very interesting note about AWS lambda - I'm having this error when I have it hosted...