You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lando init
? From where should we get your app's codebase? acquia
? Enter an Acquia API token key, visit https://cloud.acquia.com/a/profile/tokens to create one [custom token goes here]
? Enter corresponding Acquia API token secret [hidden]
ERROR ==> Cannot read property 'data' of undefined
I can pull a new repo down using git but lando pull and/or lando rebuild are also impacted by this problem.
I am running lando 3.6.4. I've been able to replicate this problem on a completely new install on a Windows and Mac Computer from both an internal and external network. This rules out local machine issues, network issues and generally points to a problem with either lando and/or the Acquia integration. This worked in the past and I've not had issues before.
I walked through all the install instructions thoroughly. I also have opened an Acquia case regarding this issue: 00861474.
The text was updated successfully, but these errors were encountered:
lando init
? From where should we get your app's codebase? acquia
? Enter an Acquia API token key, visit https://cloud.acquia.com/a/profile/tokens to create one [custom token goes here]
? Enter corresponding Acquia API token secret [hidden]
ERROR ==> Cannot read property 'data' of undefined
I can pull a new repo down using git but lando pull and/or lando rebuild are also impacted by this problem.
I am running lando 3.6.4. I've been able to replicate this problem on a completely new install on a Windows and Mac Computer from both an internal and external network. This rules out local machine issues, network issues and generally points to a problem with either lando and/or the Acquia integration. This worked in the past and I've not had issues before.
I walked through all the install instructions thoroughly. I also have opened an Acquia case regarding this issue: 00861474.
The text was updated successfully, but these errors were encountered: