-
Notifications
You must be signed in to change notification settings - Fork 203
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
clr_exception_system.overflowexception_80131516_modernflyouts.exe!unknown #35
Comments
I really don't know a bit about it 😅. How can I reproduce this on my machine? |
I'm not sure, unfortunately that's all MS store provides |
Does the app even work? |
Seems to, over 400 users who haven't reported a problem. |
400 users? Really? Has the v0.4.0 been released? |
489 total installs, 20 reported crashes, 89 inactive users (uninstalls) |
not yet was waiting to fix non x86 bug first |
When will v0.4 be out in MS Store? I know it takes a while. Next time, @ShankarBUS , release the MS Store version first. When it comes out, then release GitHub version. It will help in consistency. |
@Samuel12321, is it out yet?
Yes! that's how it should be |
I checked on MS Store right now, it still has version 0.3.3. I think it might take a while. |
Yes the same for me. But please be patient 😁 |
i released the update to the MS store this morning (8 hours ago) but it is still in certification testing. |
Why is this closed @Samuel12321? Is it fixed? |
My mistake, i was looking through store failures log, and this one had disappeared. Turns out it was just on the second page that didn't see. |
Hey @Samuel12321, I guess these exceptions shouldn't happen now. Could you verify? |
The bug must have been fixed with #113. I'm kinda sure this wouldn't happen in the future. Please verify 😄. |
yes this is no longer being reported. |
Microsoft Partner centre app analytics has revealed that this is the second most common bug:
clr_exception_system.overflowexception_80131516_modernflyouts.exe!unknown
stackTrace.txt
Bug occurred on OS build: 10.0.19041.508
@ShankarBUS Any ideas what might be causing this?
The text was updated successfully, but these errors were encountered: