Forced Trial

[iamart]

I never asked to be signed up for trial, why are you giving one??
Also if you click cancel when signin window appears after extension install - you can't use extension anymore, there's no option to signin afterwards. Reinstalling doesn't help, so have to delete the whole cache.

[justinrobots]

Hi @iamart , can you please provide more information so we can understand the issues you're describing?

I never asked to be signed up for trial, why are you giving one??

GitLens won't start a trial automatically, only when you take an action that requires you to create an account (sign-up, integration connections, etc.). Did you take any of those actions? Are you talking about the graph preview, or something else?

Also if you click cancel when signin window appears after extension install - you can't use extension anymore, there's no option to signin afterwards. Reinstalling doesn't help, so have to delete the whole cache.

GitLens will not ask you to sign in to continue the installation process, and sign-in is not required to use GitLens. Which sign-in window are you referring to? Do you have any screenshots or videos that can help understand your issue?

[iamart]

After installing an extension, this modal pops up:

Clicking cancel disables extension; clicking open and after signing in, vscode welcomes with this modal:

I'd guess desktop behaviour would match, but this is in vscode.dev.

[justinrobots]

Thanks for the additional information @iamart and for bringing this to our attention. The team discussed this morning and we suspect this may be an issue with GitLens needing to access repo info from GitHub in the browser and triggering a flow to connect the GItKraken <-> GitHub integration to get that information. This is not expected behavior, so I've created #3938 to investigate.