-
Notifications
You must be signed in to change notification settings - Fork 2
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
Claim Gas option not available. #165
Comments
Hi there! Which version are you using? This kind of issue was not being identified with version 3.0.2 for example. You can try leaving your Ledger connected (and related Ledger app open) and then access your Ledger wallet on Neon Desktop, you should be able to see your balance and claim gas. You can also join our discord server for a more direct assistance :) |
On the off chance that someone else will run into the same issue, this sounds like the ledger is not connected, the ledger app (NEO, not NEO N3) is not open on the ledger, or (for whatever reason) the connection to the ledger / app is not recognised. If the NEO app is not connected, Neon Wallet will neither display claimable GAS nor the "Claim GAS" button: Once the ledger is connected correctly, the Neon Wallet will display claimable GAS and the "Claim GAS" button. I would like to propose that the Neon Wallet should always display the button and additional text to provide status feedback to the user. If the ledger is not connected, the "Claim GAS" button could be greyed out, and the text could inform the user that the ledger needs to be connected first. Similar to this mock-up here: Regards, |
Hi,
On Reddit a few have been posting about a missing claim gas option.
To give more context, i'm also experiencing the same issue.
Like myself and someone else posted they are using a Ledge wallet. Could the missing option be related to hardware wallets?
Not only can i not claim now, i am unable to see pending gas awaiting to be claimed.
This is on the Mac OS desktop client
Thanks
The text was updated successfully, but these errors were encountered: