Replies: 3 comments 19 replies
-
|
@mtdvlpr Any idea? Don't know how to contact you directly ... |
Beta Was this translation helpful? Give feedback.
-
|
@mtdvlpr, I have the same problem, however, I edited the file that is in the cloud ForcedPrefs.json. This issue occurs because this day and time change to meetings is not saving directly to the cloud. |
Beta Was this translation helpful? Give feedback.
-
|
@stepstra I'd need more information. Your prefs, a video or reproduction steps. Are you using a congregation sync server? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, won't be home before 15:00 |
Beta Was this translation helpful? Give feedback.
-
|
@stepstra, 15:30 then? |
Beta Was this translation helpful? Give feedback.
-
|
Great |
Beta Was this translation helpful? Give feedback.
-
|
@mtdvlpr Ready to go now. Just waiting for your session-code ... |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
For all interested parties: I found the cause of the bug (with help from @stepstra). It only goes wrong when you try to change the meeting time without changing the minutes (e.g. 13:00 to 10:00). A workaround is to change it to 10:30 first and then change it to 10:00. I'll release a fix for this as soon as I tackled the bug! |
Beta Was this translation helpful? Give feedback.
-
|
The fix has been released in v24.2.0 |
Beta Was this translation helpful? Give feedback.
-
Anyone got an idea why that is?
Beta Was this translation helpful? Give feedback.
All reactions