-
Notifications
You must be signed in to change notification settings - Fork 26
Error:Invalid association handle
trying to get build service to recognise registered snap
#952
Comments
Hi @Ads20000, thank you for detailed bug report. "Invalid association handle" error usually shows up when there is some problem with user session. Could you sign out both from build.snapcraft.io and Ubuntu SSO (by going to https://login.ubuntu.com/ and clicking Log out)? Let us know if problem persists. |
Signing out from both sites and then signing in from the button on the build service worked, thank you, though I don't know how it got to that state in the first place. Also I still had to register the name via the GUI even though I had it registered with |
I believe this is a duplicate of #623 |
Summary
I’ve registered my snap using snapcraft register gifcurry-ads20000 but the build service doesn’t recognize that I have that name registered (that’s the name in my snapcraft.yaml) and then errors out when I try to log in via SSO.
Also reported on the forum.
Process
This is the process I went through:
snapcraft.yaml
to an actual one that the build service acceptsappname
name
in thesnapcraft.yaml
asappname-developername
snapcraft register appname-developername
Current and expected result
Current
I hit Sign In... and get taken to Ubuntu SSO. I log in there, then I get one of the following errors:
As you can see, my
git-iplayer
repo is registered asgit-iplayer-ads20000
and the build service has no problem with that (except the build doesn't work because of a bug I've failed to fix, ignore that).And here's the proof my
snapcraft.yaml
has thegifcurry-ads20000
name.Expected
The build service should just see that I have the repository registered.
Screenshot
See above
The text was updated successfully, but these errors were encountered: