-
• #2
I guess it is kinda to be expected because the setting.json file will be deleted on update?
This is most likely default behavior of the app loader, or maybe it is intentional to prevent unwanted side effects between versions.
Either way, I guess @Gordon could work around this. Might take him a little way to comment on this due to Holidays, I guess early Jan next year.
-
• #3
It actually looks like a bug:
setting.json
is listed as adata
file: https://github.com/espruino/BangleApps/blob/a8ccc840b7f267fe2c98750a442d0c05c78635d1/apps.json#L180
So it should not be overwritten if already present on the watch. -
• #4
I've been experiencing this too.
-
• #5
I think this should fix it: https://github.com/espruino/EspruinoAppLoaderCore/pull/6
(mandatory "urgh, submodules") -
• #7
updating Qalarm did rest to default its json file too.
-
• #8
It also uses the data tag, so that should be fixed with the pull request from rigrig.
-
• #9
Great - thanks! Just merged :)
Every time the settings app is updated I have to redo all the settings which takes quite some time.
Is this expected? It would be great if the current settings were saved before an update and restored afterwards.