supermaven-inc/supermaven-nvim
1
0
Fork 0
Code Issues 56 Pull requests 13 Projects Releases Packages Wiki Activity Actions

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

New issue
Open
opened 2024-06-28 13:04:26 -04:00 by TomChv · 7 comments
TomChv commented 2024-06-28 13:04:26 -04:00 (Migrated from github.com)
Copy link

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 :/

I just installed SuperMaven Nvim plugin and I'm subscribe to pro but for some reason, when I type `SupermavenUsePro`, I get the error: ```shell 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 commented 2024-06-28 18:40:36 -04:00 (Migrated from github.com)
Copy link

As mentioned here you need to logout first, then try Pro https://github.com/supermaven-inc/supermaven-nvim/issues/39#issuecomment-2143846460

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

As mentioned here you need to logout first, then try Pro https://github.com/supermaven-inc/supermaven-nvim/issues/39#issuecomment-2143846460 > Seems like the flow is to run SupermavenLogout first and then run SupermavenUsePro after.
👍 1
frontendwizard commented 2024-07-29 15:26:36 -04:00 (Migrated from github.com)
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?

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?
👍 4
arjunkomath commented 2024-07-29 17:54:21 -04:00 (Migrated from github.com)
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

> 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
MaciekLeks commented 2025-04-04 10:07:57 -04:00 (Migrated from github.com)
Copy link

I’d like to mention that today I encountered the same issue, and neither logging out nor reinstalling Supermaven worked. Previously, when it was functioning, it displayed a modal window with a URL, but now there’s no dialog window. What could have gone wrong?

P.S. Free version does not work either.

env: lazyvim

I’d like to mention that today I encountered the same issue, and neither logging out nor reinstalling Supermaven worked. Previously, when it was functioning, it displayed a modal window with a URL, but now there’s no dialog window. What could have gone wrong? P.S. Free version does not work either. env: lazyvim
gsouf commented 2025-05-05 07:00:38 -04:00 (Migrated from github.com)
Copy link

Same here, just installed, used the instructions in this ticket, tried restarting neovim, restarting super manven ,etc....

When I logout it shows me an url to activate. I do activate and get a success message from the browser. But then in neovim it does not seem to work at all. I see no completion nothing..and when I run :SupermavenUsePro it says

Could not find an activation URL
Same here, just installed, used the instructions in this ticket, tried restarting neovim, restarting super manven ,etc.... When I logout it shows me an url to activate. I do activate and get a success message from the browser. But then in neovim it does not seem to work at all. I see no completion nothing..and when I run `:SupermavenUsePro` it says ``` Could not find an activation URL ```
MaciekLeks commented 2025-05-05 07:47:22 -04:00 (Migrated from github.com)
Copy link

In my case the problem was related to executable permission for the binary (~/.supermaven/...). I had changed it accidentally and forgot that there is a dot directory related to Supermaven. So chmod +x helped. Now I've stopped using Supermaven because I've switched to Doom Emacs. Supermaven folks unfortunately don't support Emacs, but as a Vim user, Doom Emacs is worth giving it a try.

In my case the problem was related to executable permission for the binary (`~/.supermaven/...`). I had changed it accidentally and forgot that there is a dot directory related to Supermaven. So `chmod +x` helped. Now I've stopped using Supermaven because I've switched to Doom Emacs. Supermaven folks unfortunately don't support Emacs, but as a Vim user, Doom Emacs is worth giving it a try.
👍 1
Markizoid commented 2025-08-04 15:39:18 -04:00 (Migrated from github.com)
Copy link

For those struggling on windows, check that the ~/.supermaven/binary/<latest_version> is in your PATH
Worked for me after reinstallin the supermaven plugin

For those struggling on windows, check that the `~/.supermaven/binary/<latest_version>` is in your PATH Worked for me after reinstallin the supermaven plugin
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
old_main
rust-binary
support-array
stylua
log-changes
temp-file-download
patches
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
supermaven-inc/supermaven-nvim#68
No description provided.