-
Notifications
You must be signed in to change notification settings - Fork 139
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
App Shows Stale Data/Gets Stuck #1312
Comments
@amarinas Hello, I'm facing the same issue. |
no fix, but I just looked last night and I am getting some mobile tokens even though its the wrong location. I moved from California to Oregon so Im getting a lot of invalid witnesses and exceeded validators |
I fixed it by adding 500 000 DC on my wallet |
thank you, i also found that for 5g freedomfi you need 1 million DC(converted hnt to dc in app) to assert location for mobile AND 500k to transfer the iot side. So basically you will loose around 15 bucks for 5g. This makes sense since when i got the machine they give you a 10 hnt before all these different tokens |
Describe the bug
A large number of users on the Helium Discord, Reddit, and elsewhere, have been reporting for months various issues where the app seems to get stuck and stops pulling from the API, such as after asserting location or gain/height, initiating a transaction, etc. This affects the app up through version 4.1.0 (the latest version at the time of writing).
One such recent example:
That location assertion went through successfully the previous day, but it continued showing the above message until the user signed out and back in. Other users have shared the same screenshot, with the location having been properly asserted days or weeks earlier, but the app stays stuck there.
Another symptom of this issue is the wallet not showing any recent activity and the wallet balance remaining the same, but recent activity and the correct balance appears on Explorer.
Yet another symptom is attempted transactions failing with errors indicating an incorrect fee.
This state can always be resolved by either signing out and back in, or if that doesn't do it, then clearing the app cache or deleting the app, redownloading it, and signing back in.
To Reproduce
Unclear, but occurs frequently. I'd be happy to request any information that may be useful the next time someone reports such an issue.
Expected behavior
The app should clear out cached data and query the API again when the data's stale - maybe with a manual refresh button or pulldown action if an appropriate time can't be reliably determined programmatically.
The text was updated successfully, but these errors were encountered: