Skip to content
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

Cannot use SuperMavenUsePro: Could not find an activation URL #68

Open
TomChv opened this issue Jun 28, 2024 · 3 comments · May be fixed by #116
Open

Cannot use SuperMavenUsePro: Could not find an activation URL #68

TomChv opened this issue Jun 28, 2024 · 3 comments · May be fixed by #116

Comments

@TomChv
Copy link

TomChv commented Jun 28, 2024

I just installed SuperMaven Nvim plugin and I'm subscribe to pro but for some reason, when I type SupermavenUsePro, I get the error:

Could not find an activation URL

Is there anything I missed during my setup? I'm not sure there any API Key in supermaven :/

@arjunkomath
Copy link

As mentioned here you need to logout first, then try Pro #39 (comment)

Seems like the flow is to run SupermavenLogout first and then run SupermavenUsePro after.

@frontendwizard
Copy link

Kind of awkward this isn't mentioned anywhere, just ran into this issue as well. Should it be added to the setup instructions as a note?

@arjunkomath
Copy link

Kind of awkward this isn't mentioned anywhere, just ran into this issue as well. Should it be added to the setup instructions as a note?

Or maybe logout the user when starting Pro setup

Reflex2468 added a commit to Reflex2468/supermaven-nvim that referenced this issue Oct 24, 2024
Related to:
supermaven-inc#68 
supermaven-inc#39 

Note: I did not try this locally, just edited in GitHub, but I think this should do the trick? Basically runs the SupermavenLogout command first.
@Reflex2468 Reflex2468 linked a pull request Oct 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants