Hamilton Hardy

I am leaving this as a warning to others. I installed an older version of python to run this but was having trouble specifying which python to install it to....

@ykethan I do see an amplify-meta.json file in the root dir of ```#current-cloud-backend.zip```.

``` # Starting phase: build 2024-04-02T15:07:55.770Z [INFO]: ## Running amplify pull to generate aws-exports.js file for frontend 2024-04-02T15:07:58.003Z [INFO]: Amplify AppID found: d1f2rx89u9ycx. Amplify App name is: Napky 2024-04-02T15:07:58.052Z [INFO]:...

I double checked the current cloud backup file that I downloaded earlier and their is a parameters.json file but it is in the build folder like so ```auth/napkyff72303c/build/parameters.json```. Live Package...

Sent an email.

@ykethan Any updates on this?

I can confirm that ```amplify/backend/auth/napkyff72303c/parameters.json``` does not exist and that ```amplify/backend/auth/napkyff72303c/cli-inputs.json``` does exist in my local amplify dir. I can also confirm that is also true in the `#current-cloud-backend` dir...

While I would prefer to fix this without having to just delete the amplify folder and backend env on AWS and starting fresh, that is an acceptable work around at...

Did one more check and it doesn't look like adding storage caused any issues. @edwardfoyle @ykethan

Here is the relevant dependencies in the package.json file. ``` "dependencies": { "@aws-amplify/adapter-nextjs": "^1.0.21", "@aws-amplify/ui-react": "^6.1.5", "aws-amplify": "^6.0.18", } ``` I do not have an amplify.yml file in the local...