What’s New in Toolbox App 1.15

TL;DR: JetBrains Account integration, automatic plugins update, GitLab and BitBucket integration, improved performance, and bug fixes.

Toolbox App 1.15 is released

We are happy to tell you that the Toolbox App is now being used by over 440,000 users. We appreciate your loyalty and trust and would love to hear from you here in the comments or on Twitter mentioning @JBToolbox on which features we need to include to make your experience with the Toolbox App even better.

Here is an overview of the latest improvements to the Toolbox App.

JetBrains Account integration

The Toolbox App now uses OAuth to authenticate you in the JetBrains Account. This has a lot of benefits:

Single Sign-On: log in to your JetBrains Account once in your favorite browser and then approve the Toolbox App to access this account. There is no longer any need to enter your credentials again.

License information: the Toolbox App now lets you quickly buy a license if it can’t find one for your account. Just click on the “Buy” button and go straight to the store page.

Improved Security: the Toolbox App only has access to a limited scope of account data, and the access can be revoked at any time.

Toolbox App Security

Plugins update automatically

With Toolbox App 1.15, plugins are now stored alongside the IDE and are updated automatically together with the IDE, saving you time and removing the need for additional manual actions.
You may notice an additional “Updating plugins…” step during the installation. Since every build now has a separate plugin directory, the update is possible even when another build is running.

Updating plugins Toolbox App

Improved performance

  • We’ve significantly increased the responsiveness of the application and improved the CPU usage during updates, especially for situations where there are hundreds of projects in your Projects tab. The focus handling on Windows is now much more reliable as well.
  • Shell scripts are now generated more reliably.
  • The root cause for crashes on Windows has been found and fixed.
  • This is the last release that will support 32-bit Windows. As all our IDEs have moved to 64-bit only, it doesn’t make much sense for us to ship 32-bit binaries. If you still use the Toolbox App on x86 Windows, it will continue to work for the foreseeable future, but we urge you to upgrade to get all the latest and greatest features from all our products.

Browser Extension: GitLab and BitBucket integration

And there’s more great news! Thanks to our awesome contributors @Johannestegner and @detouched, the Toolbox browser extension now supports GitLab and Bitbucket in addition to GitHub. This means that from now on you can easily clone your GitLab, Bitbucket, and GitHub repositories right from the browser with our extensions for Chrome and Firefox. Happy coding!

As usual, many smaller fixes and improvements are included. See the full release notes for all the details.

Follow @JBToolbox to stay updated.

Download Toolbox App

Your JetBrains Toolbox App team 

This entry was posted in News and tagged , . Bookmark the permalink.

20 Responses to What’s New in Toolbox App 1.15

  1. Jógvan Olsen says:

    I’m not getting the Chrome extension to work for GitLab

    I am using the latest from Chrome webstore which is: 1.9.3781

  2. Wesley J Barton says:

    Not a bug, but a weird behavior.
    When I attempt to login to the toolbox on my Mac it opens in Chrome and offers me the Approve/Deny buttons.
    When I click on Approve I am prompted to open the Toolbox app.
    But the app I’m offered is on a Fusion VM. I had to turn off the open mac files in Windows setting in Fusion to be offered the correct Toolbox app link.
    That opened the Toolbox on my Mac and logged me back in successfully.

  3. Dave Conley says:

    Any chance of getting file associations to work when apps are installed with the toolbox app? Installing rider standalone is fine but through toolbox the sln and csproj files have no association

  4. Awesome to be mentioned in a blogpost by jetbrains! One item on the bucketlist done! ;D
    Although, my twitter handle is incorrect, hehe, it´s @_JiTe_ (although my github account name is @johannestegner as that imposter (just kidding, just another one with same name) account on twitter!!)).

    Great release! :)

  5. Yuri says:

    Can you add the ability to apply also for other gitlab url?
    We have a community edition installed in our servers with another domain, but the app doesn’t apply.

    • Victor Kropp says:

      Here is the similar and related request https://youtrack.jetbrains.com/issue/TBX-1264
      Extension detects supported services by URL, which is also required to be listed in permissions in manifest. Supporting local servers at arbitrary URL will require much more sophisticated detection algorithms and much broader permissions, which is the blocker as of now.

  6. Michał says:

    Stopped working. It says it cannot connect to server.
    Log files says:
    “Host not found toolbox-internal-feed.labs.intellij.net, skipping http://toolbox-internal-feed.labs.intellij.net/feeds/v1/internal-feed.feed.xz.signed

    • Anna Filippova says:

      Sorry for the inconvenience. Please send Toolbox App logs (сlick the metal nut icon on the right-hand side of the Toolbox App | Show Log file) to toolbox-support at jetbrains.com.

  7. Josh Koehler says:

    How does the “Automatic plugins update” action interact with the plugin configuration files listed here (https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs)? Does one location override the other?

  8. Roland Illig says:

    Yay, I really like the feature of updating the plugins automatically. I had almost filed an issue for that, but was too lazy. :)

  9. Joshua Koehler says:

    How does the “Automatic plugins update” interact with the plugin directories listed in this article? https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs. Does that article still apply for plugins migrated by the toolbox?

  10. shawn says:

    toolbox can generate shortcuts under linux .local/bin which is handy, what about toolbox itself? can it creates a shortcut for itself too? so I don’t need put a long PATH just for the toolbox itself? I have to go to .local/share/…/ to invoke toolbox when I need update(no I don’t want to run the toolbox at startup automatically)

Leave a Reply

Your email address will not be published. Required fields are marked *