IDE name and version: Eclipse IDE for C/C++ Developers 2026-03
SonarQube for Eclipse plugin version: 12.0.0.84623
Programming language you’re coding in: C/C++
Is connected mode used:
SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): SonarQube Cloud
And a thorough description of the problem / question:
I’ve updated to the newest release 12.0 and for the first time in a long time I created a new Binding by connecting one of my projects to SonarQube Cloud. I noticed that when in the Connection wizard, hitting Generate token used to open the web page and fill in the token automatically (including the test if the token is valid). So the user does not have to copy the token and paste it into the text box.
This is not the case anymore, as the the web page still opens but nothing is copied:
Sadly the UX on the Connection wizard is now degraded as it is still in the state of waiting for the token and the UI is blocked until the user is hitting the “stop” icon next to the progress bar to enable the text box again (it is grayed out, alongside the Generate token button):
I’m not sure if something broke in the meantime (as I recall this is handled on SonarLint Core side) or if SQ-C (and maybe SQ-S, I cannot verify this) lost the ability to hand back the token to the IDE.
If it is the first case, please fix it, if it is the second case, then remove the UI/UX that is triggered by clicking the Generate token button where the UI elements are grayed out and the progress bar and “stop” icon are shown. Rather show some text prompting the user to head over to their browser that just opened and copy back the token.
This is supposed to work, so it’s a bug. Would you be able to send some logs to me:
from the browser, I would be interested to get the result of the request that is sent to the SQ-IDE embedded server, could you check your Developer Console > Network. I am also interested by the logs from the console.
from the IDE, I would be interested to get the verbose logs too
please find attached an archive with all the necessary info. I updated to the latest SLE Dogfooding version just incase IDE logs have everything enabled including IDE-specific Traces.
I noticed issues in the browser console regarding the requests from the webpage to the IDE endpoint. I’ve checked, I have nothing blocked or enabled that could block the connection (if it is not enabled by default by the Safari browser).
That said, we can maybe do a better job in the product to detect the running browser is Safari, disable the button and inform users. I will discuss with the team how to implement that.
Thanks for the report amigo!
EDIT: looks like it’s not possible to detect the running browser. The recommended approach is to try the request and in case of error either fallback to something else (what we already do for the token generation), or display the error (what we do for Open In IDE). So I don’t think we can do a lot better. I will consider this thread closed
Thanks for checking that. I wasn’t aware, and I honestly did not check that docs page, only the troubleshooting and SQ-C page.
I’m fine running another browser, that won’t be a big deal. Maybe adding this information to the wizard page as a hint would be a nice-to-have, as I think a link to the docs page might not be that helpful.