Softmotions / einstein-mobile

Apache License 2.0
3 stars 1 forks source link

Crashing bug I've seen many times over the years #2

Open BarryTice opened 2 months ago

BarryTice commented 2 months ago

Hello!

This Einstein game implementation is my favorite brain break, and I'm grateful for what you've put into it.

There is, however, a bug in it.

My habit, after completing a game that I know to be in my top 250 times, is to immediately go to the Statistics page and scroll to see how many times I've scored that time. If I am too quick in getting there and then scrolling down to the entry, the application crashes and completely quits. Unfortunately, while speed seems to be a significant factor in causing the issue, it is not reliably reproducible.

This issue has persisted through Android version upgrades over the years on several phones: Moto 6g Samsung S10 Samsung A35

It does not appear to make a difference whether the time entry is the first instance of that time in the statistics list or an increment to an existing time. (It's much harder to confirm the first of those these days, as the slowest time in my top 250 is 6:21.) It also does not happen every time (though I seem to have found myself moving with less haste in the last year or so to avoid the issue). The issue has only ever been noticed when I have had to scroll through the statistics list to see the update; I do not recall it ever crashing directly on statistics page open if the completion time of the latest game is quick enough to appear on the first page.

From everything I've noticed about it, when the crash occurs the new data point persists. Restarting the application and checking the statistics page shows the just-completed time in the list. (It has never crashed for me like this immediately on reopening the application this way.)

For years I avoided making the Google Games connection, declining the opportunity each time it was offered. Then once I accidentally touched the screen in the wrong place and now there is a Google Games connection to the game (which I can't find any way to remove). The connection to Google Games does not appear to have made any difference in the frequency of this issue.

Let me know if you have any questions. I will be glad to assist in any way I can. (I'm a software tester by trade.)

andrewdenisoff commented 2 months ago

hello Barry! thank you for your report! Our next goal is to release an update with the current version of the API, as the existing one is outdated. We'll see how it performs with the new version. Since this is just a pet project, I can't provide an exact timeframe for the rollout, but we will get to it!