- Le plus récent
- Le plus de votes
- La plupart des commentaires
It seems like the issue may be related to environment variables not being set correctly in the "prod" environment. A few things you can try:
Check that all required environment variables are defined in the "prod" environment settings in Amplify. Common ones include database connection strings, API keys etc.
Try running amplify pull
in your project directory to pull in any changes from the cloud and refresh the local environment.
As a troubleshooting step, you can clear the Amplify cache by running npm i -g @aws-amplify/cli
which will force it to reset locally.
Check for any errors in the Amplify logs by running amplify logs
which may provide more clues on what's failing during the content load.
As a last resort, you can delete the "prod" environment from Amplify and recreate it from scratch to start with a clean slate.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Thanks for the reply. Where would I find these env variables?
I checked and the dynamo tables were created with the "...-prod" names, but do not seem to be accessible to amplify (apparently). I am able to create items in a table using dynamodb directly in the UI.
I've done the "amplify pull" etc. multiple times, didn't help. Just tried the "npm" command, didn't help. "amplify logs" gives me "⚠️ The Amplify CLI can NOT find command: logs" oddly.
Is there a way to re-initialize the env without removing and recreating? I remember there was one point in the creating where I had to select the auth mechanism, and I choose "Amplify Console", perhaps I should have chosen the "Keys" method or some other method.