CODEWITHSUNDEEP
mockingaws-amplify
idig
idig

Reputation: 339

Amplify mock changes are now permanent after push

I am experiencing a major problem with my Vue app using Amplify!

I ran amplify mock api which included:

"aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true

in my aws-export.js file. I failed to stop the mock server (which would have removed the above line from the aws-exports.js file) and ran amplify push. I am now unable to remove this line.

Since then I am experiencing issues when running the app, for example web-socket time outs and intermittent syncing of the DataStore data.

How can I reverse these changes made by running amplify mock and which are now permanently in the backend?

Upvotes: 3

Views: 333

Answers (1)

C RICH
C RICH

Reputation: 513

I accidentally ran amplify push while I my amplify mock config was active and faced this same issue. I thought I was cooked and needed to rebuild my entire app from scratch...

Thankfully, running amplify pull reset the config to communicate with the real server instead of the mock server. Problem solved. 😁

Upvotes: 0

Related Questions