-
Notifications
You must be signed in to change notification settings - Fork 59
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
Gemini Code Assist | Sign in button does nothing #3240
Comments
Thanks @airvzxf, looks like the browser is not opened automatically on your OS - are you able to open other links from the IDE, or use browser to sign in to other extensions without having to manually open the URL? |
Yes, @ivanporty. I can open all the links from the IDE Rust Rover and other products of the JetBrains family. All of these links were open without problems, some of these were to login to web browser others for open web pages with information. If you like, we can have a meeting in Google to share my screen. |
Please submit feedback with your logs included - use status bar Gemini icon -> Submit feedback, and mention this Github issue, we will look into more details on our side. You could also attach a small screencast on how it looks for you here, thank you |
Sure. Currently, it is working because I manually copy and paste the link of the logs in my web browser. But, I'll do the Gemini feedback. |
I created the screencast and uploaded in a YouTube video. Furthermore, I sent the feedback as you mentioned. |
Thank you! We'll take a look at this |
Gemini Code Assist | Sign in button does nothing
Problem
I tried to use Gemini in Rust Rover 2024.3 but when I clicked on the “sign in” button, nothing happened.
Then, I checked the Rust Rover logs, and I got the following message. I replaced potential sensitive information from the URL with “xxxx”.
~/.cache/JetBrains/RustRover2024.3/log/idea.log
Solution
After I manually opened the URL in Firefox, I am able to go to the next step to use the Gemini's plugin.
Technical information
The text was updated successfully, but these errors were encountered: