Thanks for the report. Have you tried without BLYNK_USE_DIRECT_CONNECT ? Also can you try our beta app’s version (open google play app, search for blynk, on blynk page - scroll till ‘joint beta’ section), as it has logging support (about screen has button ‘send logs’) - so I can check the logs from your device.
I see that hardware sends another token for login: ca537FkGkxaBmBvqlFud5d6kj8HIMK8s
And due to the difference between device’s token and received token - app understands this situation as failed authentication.
Not sure, may be related but he gets his token cut so it cannot be authenticated and I get junk data while using BLE. I also use Visual Code + PlatformIO but I tried with Arduino IDE and same results, I doubt so it is platform related: Junk data appears in serial monitor and breaks blynk
I mean install Blynk app beta (open google play app, search for blynk, on blynk page - scroll till ‘joint beta’ section), and send logs from it (about screen has button ‘send logs’)
OK, sent to your email. The log contains 1 intentional disconnection and re-connection, as this is one of scenario when auth token appears in serial monitor. After connection other junk data appears.