Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Partner Licensing Platform (Developer Preview)
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Error: API Version Mismatch
CLI Version Information
Run CLI Commands on macOS Sierra (Version 10.12)
Error: No defaultdevhubusername org found
Unable to Work After Failed Org Authorization
Error: Lightning Experience-Enabled Custom Domain Is Unavailable
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Error: No defaultdevhubusername org found

Let’s say you successfully authorize a Dev Hub org using the --setdefaultdevhubusername parameter. The username associated with the org is your default Dev Hub username. You then successfully create a scratch org without using the --targetdevhubusername parameter.

But when you try to create a scratch org another time using the same CLI command, you get this error:

What happened?

Answer: You are no longer in the directory where you ran the authorization command. The directory from which you use the --setdefaultdevhubusername parameter matters.

If you run the authorization command from the root of your project directory, the defaultdevhubusername config value is set locally. The value applies only when you run the command from the same project directory. If you change to a different directory and run force:org:create, the local setting of the default Dev Hub org no longer applies and you get an error.

Solve the problem by doing one of the following.

  • Set defaultdevhubusername globally so that you can run force:org:create from any directory.

  • Run force:org:create from the same project directory where you authorized your Dev Hub org.

  • Use the --targetdevhubusername parameter with force:org:create to run it from any directory.

  • To check whether you’ve set configuration values globally or locally, use this command.