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
The following can sporadically occur after setting up a new Launcher profile:
Set up password and initialize lair
Installing DevHub (automatically)
From then on, zome call signing consistently fails in the DevHub with the error "Query returned no rows" that's thrown by the sign_by_pubkey function of the lair client.
Apps installed afterwards from the filesystem work fine, no zome call signing errors
In this case, the only thing that helps is a factory reset and some luck that the same thing does not happen again.
Additional context
In a case where this occured, I checked the keys stored in Lair via list_entries() and verified that the DevHub's public key is missing.
The text was updated successfully, but these errors were encountered:
Describe the bug
The following can sporadically occur after setting up a new Launcher profile:
sign_by_pubkey
function of the lair client.In this case, the only thing that helps is a factory reset and some luck that the same thing does not happen again.
Additional context
In a case where this occured, I checked the keys stored in Lair via
list_entries()
and verified that the DevHub's public key is missing.The text was updated successfully, but these errors were encountered: