You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to change the date results in "Invalid Date" appearing where the date is and saving new date results in "Transport error: Not an integer" appearing in a notification pop-up. No choice but to cancel with no date change.
Steps to reproduce
1: make a note
2: save it
3: go to edit the note
4: click on the date
5: select a different date -> Results in the words "Invalid Date" appearing where the date was and the calendar does not close. Even if you select the same date, this does not change.
6: Click Save -> Results in a notification box that says "Transport error: Not an integer"
7: no choice but to select cancel to get out of edit. -> Reults in the date remaining unchanged.
The version of Memos you're using.
Was true in 22.3, upgraded to 22.5 and it still happens (note: In settings it says 23.0)
Screenshots or additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Attempting to change the date results in "Invalid Date" appearing where the date is and saving new date results in "Transport error: Not an integer" appearing in a notification pop-up. No choice but to cancel with no date change.
Steps to reproduce
1: make a note
2: save it
3: go to edit the note
4: click on the date
5: select a different date -> Results in the words "Invalid Date" appearing where the date was and the calendar does not close. Even if you select the same date, this does not change.
6: Click Save -> Results in a notification box that says "Transport error: Not an integer"
7: no choice but to select cancel to get out of edit. -> Reults in the date remaining unchanged.
The version of Memos you're using.
Was true in 22.3, upgraded to 22.5 and it still happens (note: In settings it says 23.0)
Screenshots or additional context
The text was updated successfully, but these errors were encountered: