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
Bug:
After I rename a custom javascript resolver, the build fails in Amplify Gen 2 console however the build & deployment are successful in local cloud sandbox environment.
Steps to reproduce:
Create an additional AppSync API (as we have exceeded 1MB size limit of Amplify data stack a long time ago)
Add an external DynamoDB database in backend.ts file and create a datasource for the AppSync API
Add a mutation in graphql schema file
Create a custom javascript resolver function and add it to backend.ts file
Deploy the changes
Now rename the resolver function
Deploy again
This time the build fails in Amplify Gen 2 console.
getIncidentAndStakeholder.js is the updated resolver file name and it is available in the code repository.
The text was updated successfully, but these errors were encountered:
Environment information
Data packages
Description
Bug:
After I rename a custom javascript resolver, the build fails in Amplify Gen 2 console however the build & deployment are successful in local cloud sandbox environment.
Steps to reproduce:
This time the build fails in Amplify Gen 2 console.
getIncidentAndStakeholder.js is the updated resolver file name and it is available in the code repository.
The text was updated successfully, but these errors were encountered: