-
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
Error constructing assert location transaction when asserting location for the first time #1077
Comments
I have been able to workaround this issue by issuing location/antenna update commands through by using the CLI wallet |
what is your hotspot's name? I want to see if I can find some clues/hints even though you were able to submit the transaction via CLI. |
this is also a regression so we'll look into it regardless. thanks for reporting. |
Hotspot's name is Little Seaweed Crow. The problem still exists on my other hotspots (Damp Marigold Cottonmouth and Howling Peanut Halibut) that I haven't deployed yet. |
The error constructing transaction is still happening on those other Hotspots? Are they plugged into/synced to the chain yet? |
Yes, one of them is plugged in and completely synced, one of them is not. Has been going on for me at least for almost a month before I was suggested the CLI wallet route |
Hi my hotspot name is Fast Syrup Goat, I cannot find the hotspot in the App nor in the helium map. Please help |
Could someone please let me know what is the next step to bring the RAK Minter V.2 to the helium network? |
@will-deng are the other two hotspots RAK v1.5 as well? |
@will-deng would you be able to give one of the two left another try? |
Location Asserting error no longer there, it’s is online now but it is saying it’s been relayed, any help appreciate it. |
@tyler-whitman no luck, the other two hotspots are mntd goldspots so I think these are RAK v2s |
@will-deng looks like you were able to assert them - what changed? |
Re asserted the location.
…On Thu, Dec 9, 2021 at 11:51 AM Coco Tang ***@***.***> wrote:
@will-deng <https://github.com/will-deng> looks like you were able to
assert them - what changed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1077 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIENQQI6XQLMW3NTMVHQZJLUQDM7VANCNFSM5H3FX5EQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
closing as this has gone stale and looks to be resolved. |
Hi there, just got a brand new MNTD Gold miner, got this error on my very first attempt to register.. I have repeated the registration a few times now, every time it says registering and later on its not there.. Sometimes I get the above mentioned error message in a popup, sometimes I get it asynchronously in the IOS app notifications. Not sure how to proceed. Any hints? (remember the hotspot is not listed in the app for me to do any manual asserts) |
Let me know if you found a resolution. I'm facing the same issue with a Midas-962. It does appear this has not been closed. |
I'm having this issue with a brand new Midas-926 miner when registering for the first time. |
I updated my location a second time and it seems to have finally gone through. The phone app says "Updating location" still, but I can find my miner on the Helium Explorer site. |
If it's stuck showing 'Updating location', update the app to 4.1.0 if it's not already on that version, then sign out, then sign back in. |
Signing out and back in, worked to fix the Updating location issue. Thanks dude! |
No problem - I've already submitted an issue for it (#1312); hopefully it gets resolved soon! |
Describe the bug
Error constructing assert location transaction when asserting location for the first time.
To Reproduce
In the Helium app, either on Android or iOS:
Expected behavior
Hotspot's location is asserted
Screenshots
Can't take screenshots due to security policy but the Error after hitting submit is as follows:
Error
There was an error constructing the Assert Location trnsaction. Please try again.
Smartphone (please complete the following information):
Additional context
This was performed on a RAK hotspot v1.5. A user in discord said that their Bobcat was also exhibiting the same issue when trying to assert location for the first time. I was able to assert the location for a MNTD Goldspot miner recently but no luck on this device unfortunately. I have also tried changing from StakeJoy API to Helium API but that did not work either.
Update: Cannot update antenna info either. Same error
The text was updated successfully, but these errors were encountered: