We are having a livesite issue here, so please help urgently.
New devices being configured (connected, claimed, flashed) have the “current_build_target” set as 0.4.9. This change started sometime in the last 24-36 hours. I believe we used to have the build target set as 0.6.0 or 0.6.1 until very recently (devices configured early this week have this build target). The 0.4.9 firmware target breaks our current application and the devices get stuck indefinitely in safe-mode.
If we use the IDE and change the target to 0.6.0, the application is flashed correctly and the device comes back online. With 0.4.9 (or 0.6.2) as target, while it appears that the flash is successful, the device gets stuck in safe-mode.
Here’s an example of a new device with the build target set as 0.4.9
looping in @Dave in case he is aware of any rogue instance of the firmware endpoint.
Thanks in advance.