mirror of
https://github.com/dabeani/meshcoreterm.git
synced 2026-10-31 10:11:57 +01:00
All contacts lost on upgrade #271
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/meshcore#271
Reference in new issue
Block a user
Describe the bug
Upgrading to version 0.9.12.3 removes all known contacts (not the channels). Was probably introduced in 0.9.12.2 where I also lost all contacts on upgrade too.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
0.9.12.3
To Reproduce
Steps to reproduce the behavior:
Additional context
I took a backup after the first restart (the one in which all contacts are shown). The contacts.bin file has size 0. Restore couldn't bring the contacts back of course.
No big deal. When the contacts are added again, they persist.
Additional info: On my second device, all contacts disappeared on the first boot in the new firmware, not in the second as described in my first report. So they are really lost after flashing.
Thank you for this important informations.
Since 0.9.12.1 there is a first boot migration implemented to update the Contacts to a newer format to keep more additional informations. Nevertheless, i had 3 tdecks to test and all of them migrated without issues. I will dig into it later, but good to know for other users. I usually create a backup with my connected mobile, and export the data, if something goes wrong, i can import data via the Mobile.
That was exactly what I did, so really no big deal!
Ive only just seen the latest update and due to me seeing your post i copied the data files from the mcterm folder to re introduce in the update. Thanks christian for the heads up all updated now and no contacts lost
Just to know:
Can you confirm that for you the contacts where not lost when updating from 0.9.12 to 0.9.12.1, or did you not do that step?
I am still at 0.9.12 and for now holding back any updates. If it did not happen for you with 0.9.12.1, I would try that at least.
I'm nearly 100% sure, I didn't lost the contacts from 0.9.12 to 0.9.12.1. But make a backup with the companion app first. Just to be safe.
Ive already moved away from mcterm for a while as im sick of fighting with the application if its not the time syncing its losing all the contacts and other weird behaviours. Holding back on updates isnt a bad idea at all! ive left in place the ability to add the application back in should i want to re explore its nuances,
i tried to back up on 0.9.12.3 but non of the buttons on the back up page did anything so didnt bother going any further with it
I’m having the same issue with BavKup on the Indicator. I’m also having trouble switching from internal storage to the SD card’s external storage under ‘Global’ at the top; it starts to freeze up and become unresponsive, and the system freezes briefly.
Bernhard works hard on trying to keep the application to work across hardware, im gratefull for his hard work in bringing a great app to meshcore but am finding it a bit of an ordeal keeping it working ! maybe its because im using the launcher application maybe machine specific. i dont know but after losing all my contacts again last night pushed me to removing the application for now. I may come back at some point but for now im going to use ripple ultra or a time where im not using the launcher app as i cant rule out that might have something to do with it!
OK, I updated.
Contacts were not lost, but some(!) pre-defined scopes got deleted and channels in
Mgmg→Channelswere re-ordered.Also, DM messages were lost as well as messages inside channels.
And scope assignments to channels were messed up (got different scopes assigned).
I use M5Launcher, too.
Could it be that enabled WebUI deletes all contacts, and when you have WebUI disabled, contacts do not get deleted?
See #286.
This report predates several persistence fixes that shipped in v0.9.14 (identity recovery order at boot, factory-reset rework, and the NVS key bug above).
Has this been fixed, @christianprim? Then I suggest closing this issue.
Regards!