-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error when starting new Pokemanki deck #44
Comments
Having the same bug ... despite the update released today Error Caught exception:
**This is my test account, no active add-ons except the one I'm troubleshooting |
I have no other add-ons, and I have exactly the same problem. Please, can you debug it, i reeeeeally need a pokemon team :( |
Troubleshooting Checklist
Replace the space between the parentheses with an x to mark the items as verified.
If you have an issue that has already been reported, join the discussion of the existing issue instead of creating a new one.
Describe the bug
I did a fresh install of the addon this morning, 9/18/2023. I have never used Pokemanki before. When I go to the Stats tab, I am prompted to choose a deck for my starter Pokemon, but then the addon crashes.
If Anki shows an error message, copy and paste it between the backticks below.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected a popup for started Pokemon to display after the starter deck prompt.
What have you tried?
I made a comment in a previous issue but that issue didn't end up being related to this bug, so I thought maybe it would be fixed with the update. It seems like there's an issue with the starter Pokemon
QTMessageBox()
being out of scope?Screenshots
If applicable, add screenshots to help explain your problem.
Information about your set-up
Open Anki, go to Help > About and click on "Copy Debug Info". Paste the result between the backticks below.
What operating system are you using?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: