Tooling API no longer being used when saving

[Jeff Hube]

In Settings, I have all options checked under "Prefer Tooling API for".

However, when I save classes or pages, the deployment is being done with the metadata api instead. I did not test lightning or static resources.

This is frustrating because while the tooling api normally saves in a couple of seconds, the metadata api has been extremely slow for me recently, with some deployments having a "Pending" status for several minutes.

[Scott Wells]

Jeff, can you add the following under Help>Debug log settings and perform a deployment:

#com.illuminatedcloud.intellij.builder.ForceComBuilder
#com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer
#com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer

then please send me the resulting idea.log (Help>Show Log in Explorer/Finder). That should tell me exactly why it's deciding to use the metadata API instead of the tooling API.

[Jeff Hube]

#!
2016-09-30 13:53:09,017 [  40389]  DEBUG - tellij.builder.ForceComBuilder - Connection is for a production org. The Metadata API will be used regardless of Tooling API preferences. 

It thinks it's a production org. It's on na35, but it's actually a trialforce org, so the tooling api would still work fine.

[Scott Wells]

Ah, yes...right now it's pretty conservative about where it will use the tooling API. Currently it limits usage to Developer Edition and Sandbox orgs. I'm going to be posting a small update later today. Let me see if I can give you a way to override that when you know that your org can be used with the tooling API.

[Jeff Hube]

That would be great, thanks.

[Scott Wells]

Spinning a new build now that will be posted very shortly.

[Scott Wells]

Delivered in 1.7.4.6. Uncheck Use Salesforce-reported organization type under Use Tooling API for and make sure that your connection's configured organization type is set to something other than Production.