We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next day starts at should be consistently at 4 am on both Ankidroid and Windows.
After syncing, next day starts at 6 pm on Ankidroid, and 4 am on Windows. This happens even after setting next day starts at to 4 am on Ankidroid.
AnkiDroid Version = 2.9.5
Android Version = 10
ACRA UUID = 22093a8d-3099-421d-b128-30c8204cad98
Enter an [ x ] character to confirm the points below:
[ x ] I have read the support page and am reporting a bug or enhancement request specific to AnkiDroid
[ x ] I have checked the manual and the FAQ and could not find a solution to my issue
[ x ] I have searched for similar existing issues here and on the user forum
The text was updated successfully, but these errors were encountered:
This is indeed a problem - there is at least one issue open already that you should follow for updates #5380 - sorry it is affecting you
Sorry, something went wrong.
No branches or pull requests
Reproduction Steps
Expected Result
Next day starts at should be consistently at 4 am on both Ankidroid and Windows.
Actual Result
After syncing, next day starts at 6 pm on Ankidroid, and 4 am on Windows. This happens even after setting next day starts at to 4 am on Ankidroid.
Debug info
AnkiDroid Version = 2.9.5
Android Version = 10
ACRA UUID = 22093a8d-3099-421d-b128-30c8204cad98
Research
Enter an [ x ] character to confirm the points below:
[ x ] I have read the support page and am reporting a bug or enhancement request specific to AnkiDroid
[ x ] I have checked the manual and the FAQ and could not find a solution to my issue
[ x ] I have searched for similar existing issues here and on the user forum
The text was updated successfully, but these errors were encountered: