You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When claiming an L2 planet, it appears as though if you claim it too quickly (i.e. before the roller runs from the initial claim) it will not include the keyfile in the downloaded passport. That, or the instructions given upon claiming are incorrect.
To Reproduce
Steps to reproduce the behavior:
Go to 'bridge.urbit.org/planet-claim-link-path
Click on 'claim'
Quickly download passport and verify master ticket
See error
Expected behavior
I would expect the keyfile to be included in the passport download if that is what the final instruction suggests; or for the instructions to point me towards how to generate my keyfile directly from bridge.
Desktop (not expected to be relevant):
OS: macOS Monterey 12.5
Browser: Brave
Login method (please complete the following information):
Accessing bridge via L2 invite URL
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
vvisigoth
changed the title
Disconnect on instructions and keyfile location
L2 planet passports sometimes don't include keyfile
Apr 17, 2023
Describe the bug
When claiming an L2 planet, it appears as though if you claim it too quickly (i.e. before the roller runs from the initial claim) it will not include the keyfile in the downloaded passport. That, or the instructions given upon claiming are incorrect.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the keyfile to be included in the passport download if that is what the final instruction suggests; or for the instructions to point me towards how to generate my keyfile directly from bridge.
Desktop (not expected to be relevant):
Login method (please complete the following information):
Accessing bridge via L2 invite URL
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: