-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
Settings - "Reviewing" & Deck import do not handle SchedV1 correctly #17838
Comments
I've seen this one a few times in reviews for 2.19. @mikehardy would you support a backport for a [probably simple] fix, since we've done a huge upgrade for some users with: |
I may be misreading what you mean, but at the moment the title looks misleading or incorrect to me. If I understand correctly, the error occurs just when users' collections are using V1 scheduler, not V2 scheduler. Do you have a different view on this point? |
@snowtimeglass no, fair point. Title updated EDIT: Just confirmed. It's SchedV1 |
I would definitely take a backport if it was reasonable at all, as a set of commit picks |
For what it's worth, user reports that you can create a new deck, then press on the deck, and that will update things? I'm not 100% clear on that, and I have not tested it personally - just saying that there is a report of success getting a v1 collection back to usability on 2.19... Obviously a real fix here would be preferable 😆 |
This issue is specifically for errors on the 'Reviewing' and 'Deck Import', which do not offer a path to upgrade. If the user has a reviewable deck, then they can click on that and the upgrade to V3 is offered. If the user does not have decks, the UX of upgrading would be unlikely to lead to success |
For reference of AnkiDroid (2.21alpha7) behavior: Record_2025-01-18-14-44-22_c428a0327e1e5e78cdd71c6b04816edf.mp4 |
Hi, I want to help with this issue. Please assign if it is not taken. |
Worth dropping a bug upstream for that one |
In the desktop version, the error message can be interpreted that "Please select Learn More, which is already shown in the main screen, before proceeding". This flow may have room for improvement of UX, but not so much as a bug, in my opinion. |
I think the same dialog which is prompted on the main screen should be prompted here instead of showing it as an error from backend. |
Checked for duplicates?
Does it also happen in the desktop version?
What are the steps to reproduce this bug?
Expected behaviour
A dialog like this:
Debug info
(Optional) Anything else you want to share?
No response
Research
The text was updated successfully, but these errors were encountered: