Occasional wallet version check message pops up
See original GitHub issuethe
Error checking wallet version! Please make sure you have downloaded the latest version: https://github.com/CityOfZion/neon-wallet/releases
Toast is shown, while using the latest version of the wallet
Wallet version or commit SHA: 2.0.0
Environment: macOS Mojave 10.14.1 (18B75)
Prerequisites: /
Reproduction steps: e.g.: It’s not very clear HOW this happens. I tried installing the older version and reinstalling the newest version, but it appears at most of the time when I quit the app and start it back up.
Screenshots/Video:
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
When i press button popup message showing “ Add Cards to ...
When i press button popup message showing “ Add Cards to Wallet To add cards, keys, tickets, and passes to Wallet, look for...
Read more >Some older wallets (2014 era) not correctly opened or imported
When attempting to decode this base58 encoded private key, it would end up as the incorrect length and not be correctly imported.
Read more >How to Fix your Card, App, Internet, and Bluetooth Issues
If your CoolBitX app's software version is outdated, the app will usually display a popup message asking you to update it to the...
Read more >How to Add Your COVID Vaccine Card to iPhone's Apple Wallet
For users with a downloadable file, pull it up on your phone and then tap the download link. Select "Add to Wallet &...
Read more >WalletConnect Unveils the Future of Web3 Chat With Wallet-to ...
WalletConnect reveals a first look at its upcoming Chat API, which enables messaging between web3 wallets.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ranbena @comountainclimber: Implemented retry method works properly. It won’t fix the issue completely, but for sure it will make it less visible (happen more rarely).
It works only on 5xx errors. For example, retry mechanism is not triggered while:
null
as response)All cases above are handled in a way that hides notification about update and no error is shown. For example, this means that if for some reason API url would change (what is very unlikely), all users would be left without update message forever. Or if API url would be blocked with firewall, same thing would happen. Maybe we should show an error in this case that there was an issue while fetching for updates?
Cool I’m on it