Migration to new account about amplify-cli HOT 6 OPEN

Hey @fistofzen, could you provide us the full error message printed on the terminal?
Does the project have a team-provider-info.json?
Tried reproducing the error message with and without a team-provider-info.json wile selecting a new profile created a new app.

from amplify-cli.

I tried every way,
First I deleted the team-provider-info.json but still the same error. app id not found.
The system trying to find old app id in the new account but it not exists. And as a result login is not successful.

from amplify-cli.

@fistofzen tried reproing this issue with a new account and removing the team-provider-info.json then run amplify init selecting the new profile but did not observe any init failure.
Are you referring to the warning ⚠️ Failed to resolve AppId. Skipping parameter download.?
the warning should not effect the project creation but warns the user it unable to find an appID associated and created a new application on the console.
are you observing an other error messaging after this warning?

from amplify-cli.

after apmlify init,
I am going like that.

Received error [Error: Command was killed with SIGSEGV (Segmentation fault): yarn --version] running command [yarn --version]

from amplify-cli.

ShellCommandExecutionError: Received error [Error: Command was killed with SIGSEGV (Segmentation fault): yarn --version] running command [yarn --version]
at execWithOutputAsString (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/shell-utils.js:38:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getYarnPackageManager (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/packageManager.js:131:36)
at async runPackageManagerInstall (/snapshot/amplify-cli/build/node_modules/amplify-nodejs-function-runtime-provider/lib/utils/legacyBuild.js:70:28)
at async installDependencies (/snapshot/amplify-cli/build/node_modules/amplify-nodejs-function-runtime-provider/lib/utils/legacyBuild.js:67:5)
at async Object.buildResource [as build] (/snapshot/amplify-cli/build/node_modules/amplify-nodejs-function-runtime-provider/lib/utils/legacyBuild.js:44:13)
at async buildFunction (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/buildFunction.js:29:22)
at async prepareResource (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:420:33)
at async prepareBuildableResources (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:416:5)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:177:5)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:137:16
at async Promise.all (index 0)
at async providersPush (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:133:5)
at async AmplifyToolkit.pushResources (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:107:13)
at async Object.executeAmplifyCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:194:9)
at async executePluginModuleCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:139:5)
at async executeCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:37:9)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:121:5)

Session Identifier: 335820ba-9e85-4be9-8e54-c08a8b701d7d

from amplify-cli.

@fistofzen could you provide us the local yarn version being used. Could you trying using the yarn version 1.22.19 and retry the command.

from amplify-cli.