Error while running amplify pull in headless mode

[fkoner]

Describe the bug
While executing the pull command using the headless configuration, the following error occurs:

2020-09-02T17:27:13.675Z [INFO]: TypeError: Cannot convert undefined or null to object
                                 at Function.assign (<anonymous>)
                                 at confirmFrameworkConfiguration (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-javascript/lib/configuration-manager.js:102:12)
                                 at confirmConfiguration (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-javascript/lib/configuration-manager.js:69:9)

Amplify CLI Version
4.28.1

To Reproduce

1. Export environment variables:

export REACTCONFIG={"SourceDir":"src","DistributionDir":"build","BuildCommand":"yarn run build","StartCommand":"yarn run start"}
export AWSCLOUDFORMATIONCONFIG={"configLevel":"project","useProfile":true,"profileName":"default"}
export AMPLIFY={"projectName":"headlessProjectName","appId":"xxxxxxxxxxxxxx","envName":"dev","defaultEditor":"code"}
export FRONTEND={"frontend":"javascript","framework":"react","config":{"SourceDir":"src","DistributionDir":"build","BuildCommand":"yarn run build","StartCommand":"yarn run start"}}
export PROVIDERS={"awscloudformation":{"configLevel":"project","useProfile":true,"profileName":"default"}}

2. Run ampliy pull with exported variables:

amplify pull \
  --amplify $AMPLIFY \
  --frontend $FRONTEND \
  --providers $PROVIDERS \
  --yes

Expected behavior
Ensure that the amplify pull command is executed. For previous versions (e.g. version 4.28.0) it has worked correctly.

Screenshots

Desktop (please complete the following information):

• OS: [Ubuntu, MacOSX]
• Node Version: 10.20.1 (local) 10.16.0 (amplify console)

Additional context
The script we are dealing with is very similar to this:
https://docs.amplify.aws/cli/usage/headless#sample-script-3

The bug appears both in our local environment and in the amplify console, it is related to the command line, and not a bug associated to the amplify console.

I don't know if something changed between version 4.28.0 and version 4.28.1, but with this patch we were presented with this error this morning.

If you require more detail I can share my headless script.

Thanks in advance.
Paco

[akshbhu]

Hi @fkoner

I tried with the sample script and demo project and it is working fine for me. Can you elaborate more on following points:

• Is it working for you in version 4.28.0?
• Can you tell the details what resources you have added before so that I can repro this issue?

[cristhian-boc]

There is a bug on the CLI. We are getting the following error: Unsupported javascript framework: react-native. I can see that somebody changed the framework-config-mapping.js file. You are not returning the configs as in the past.

Before:

Current:

And the configuration-manager.js file is trying to read the keys from that module.exports:

if (!Object.keys(frameworkConfigMapping).includes(inputParams.framework.toLowerCase())) {
      context.print.warning(`Unsupported javascript framework: ${inputParams.framework}`);
      inputParams.framework = 'none';
    }

So that is a breaking change, and maybe is the answer to solve this issue too.

This is our config for the frontend configuration:

FRONTEND="{\
\"frontend\":\"javascript\",\
\"framework\":\"react-native\",\
\"config\":$REACTCONFIG\
}"

We will use @4.26.0 in the meantime.

[fkoner]

@akshbhu

I updated the issue, sorry, is not working in version 4.28.1, in previous version 4.28.0 it works.

[akshbhu]

Yup , I have reproduced this . Thanks for your insights @cristhian-boc

[fkoner]

@akshbhu
@cristhian-boc
These commits

5debb76

bb06162

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.