Skip to content
This repository has been archived by the owner on Jun 11, 2020. It is now read-only.

Error:Invalid association handle trying to get build service to recognise registered snap #952

Closed
Ads20000 opened this issue Sep 11, 2017 · 5 comments

Comments

@Ads20000
Copy link

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:

Current and expected result

Current

screenshot from 2017-09-10 10-40-20

I hit Sign In... and get taken to Ubuntu SSO. I log in there, then I get one of the following errors:

screenshot from 2017-09-10 10-40-31
screenshot from 2017-09-10 10-39-29

As you can see, my git-iplayer repo is registered as git-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 the gifcurry-ads20000 name.

Expected

The build service should just see that I have the repository registered.

Screenshot

See above

@bartaz
Copy link
Contributor

bartaz commented Sep 11, 2017

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)?
Or try to sign in and register name in browser Incognito/Private mode (to make sure you are using clean session)?

Let us know if problem persists.

@Ads20000
Copy link
Author

Ads20000 commented Sep 11, 2017

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 snapcraft register but I guess that wasn't so big an issue.

@joedborg
Copy link

joedborg commented Feb 28, 2019

I believe this is a duplicate of #623

@Ads20000
Copy link
Author

I'm confused, #952 is a duplicate of #952?

@joedborg
Copy link

I'm confused, #952 is a duplicate of #952?

Sorry, my bad, i've updated the comment

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants