Closed BubblyNetDev closed 3 years ago
I did notice that in multiple migrations of nodes the ttl field has been left out. I would assume this is intentional? When these are added into the migrations, the ttl is no longer unknown when updated and the app will not crash when sending a message.
Hi, yes there have been multiple migrations in between these versions, but should not crash the app when trying to control. I will have to debug this and see. I can't promise any dates as I have some other tasks in my plate.
Okay, I added ttl to the migrations as a fix for now.
Sorry for the delay but is fixed, tested and working on dev now.
Describe the bug Downloaded 2.4.4 and added a device, bound keys, and added subscriptions. Controlled device from 2.4.4 with no issues. Downloaded 3.1.5 and built app. Device TTL unknown and app crashes when trying to send messages.
To Reproduce Steps to reproduce the behavior:
Logs / Screenshots