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
Workaround: after running amplify push or amplify pull, the endpoint values will be correct again. However, we still need to remove "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true from aws-exports.js manually.
The text was updated successfully, but these errors were encountered:
Before opening, please confirm:
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.6
Amplify CLI Version
7.6.4
What operating system are you using?
Mac (Apple Silicon)
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
amplify mock
is not reverting aws-exports.js on termination, therefore, it still contains the mock values.Expected behavior
According to the docs: Once you stop the mock server the config files are updated with the correct cloud endpoints for your project and DangerouslyConnectToHTTPEndpointForTesting is removed from the config file.
Reproduction steps
amplify mock
amplify mock
GraphQL schema(s)
# Put schemas below this line
Log output
Additional information
Workaround: after running
amplify push
oramplify pull
, the endpoint values will be correct again. However, we still need to remove "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true from aws-exports.js manually.The text was updated successfully, but these errors were encountered: