-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[BUG]: AnkiDroid error when interacting with the API #16318
Comments
Hello! 👋 Thanks for logging this issue. Please remember we are all volunteers here, so some patience may be required before we can get to the issue. Also remember that the fastest way to get resolution on an issue is to propose a change directly, https://github.com/ankidroid/Anki-Android/wiki/Contributing |
Have you checked logcat? Package com.ichi2.anki |
Closing the issue since I was unable to reproduce again. |
Reopening. This error I got when reviewing a card with the API. |
@warleysr Could you update the first post & title with your findings? Thanks! |
Checked for duplicates?
Does it also happen in the desktop version?
What are the steps to reproduce this bug?
I'm creating an app that queries AnkiDroid database to get card content, on my main screen I show the deck list to the user. I have a instance of
AddContentApi
and call thegetDeckList()
method. Sometimes when I launch my app a Toast from AnkiDroid appears saying that some error ocurred and a report was being generated.UPDATE:
The AnkiDroid toast keeps appearing very often, sometimes when getting the deck list or when reviewing a card. Checking the Logcat I got this error:
Expected behaviour
Do not receive error messages when interacting with the API.
Actual behaviour
Toast messages on my app saying that a report is being generated, when I return to the AnkiDroid app a popup asks me if I want to send the report to developers. Even though the error occurs getting the deck list still works.
Debug info
(Optional) Anything else you want to share?
No response
Research
The text was updated successfully, but these errors were encountered: