This seems to be a bug at this point
From the Twitter conversations with PM, he is aware of it and they are working on it to fix it asap.
Current workaround is sign up for a prerelease org and then enable devhub and use that to create spring 20 scratch orgs.
Update from PM that this has been fixed now!...
This issue is due to Spring '20 and can happen with new scratch orgs too. Not all sandbox pods are affected.
The event emitter warning has nothing to do with the actual problem. The underline issue is a redirect from https://..my.salesforce.com to https://.my.salesforce.com. When redirecting to a different host, authorization headers are removed which ...
This has been happening to me since around October 2019. Running on Windows. Have a suspicion that it could be caused by a strict security settings of my Windows.
You can always copy'n'paste the URL printed for you /secur/frontdoor.jsp
On inspection I saw that the POD (instance) on which my scratch orgs exist had been upgraded to Spring '20 on Saturday.
The only solution I could find was to delete my scratch orgs and re-create them using the original aliases. Having done this the problem went away.
I guess Spring '20 doesn't play nice with Winter '20 scratch orgs.
I don't have a complete explanation for this issue, but I think the information you've supplied gives a pretty good shot at pinning down where it is located.
CumulusCI appears to me to be working correctly, and you're running the correct commands.
The issue appears to me to lie in your CircleCI YML. The YML you've shared here does not match the screenshot, ...
sfdx force:org:create takes the -v argument (not -u) to specify a Dev Hub.
I suspect that your default Dev Hub has hit its limit, while others may or may not have, but your scratch org requests aren't being routed where you intend them to. Check which Dev Hub is default by running sfdx force:org:list (it has the (D) annotation), and ensure that you use the ...
CumulusCI executes commands against the org whose name you specify with --org. If that org does not yet exist, CumulusCI creates an empty org and executes the command against it.
Before running tests, whether Robot or Apex, with CumulusCI, you'll typically build the org using a flow, such as dev_org, qa_org, or install_beta. Those flows push your project's ...