Amplify pull misses hostedUIProviderCreds in the team-provider.info file - An error occured during the push operation: Resource is not in the state stackUpdateComplete

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug Amplify pull misses hostedUIProviderCreds in the team-provider.info file. This causes a push to fail with the following cloudformation error:

UPDATE_FAILED      authxxxxxxx630360af         AWS::CloudFormation::Stack Tue Mar 10 2020 23:26:52 GMT+0000 (Greenwich Mean Time) Template format error: Unresolved resource dependencies [hostedUIProviderCreds] in the Resources block of the template

Following resources failed

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occured during the push operation: Resource is not in the state stackUpdateComplete

Amplify CLI Version 4.13.4

To Reproduce

• Add federated login to project with add auth and add fb/google oauth details.
• Then push with amplify push
• create another project in a different folder and amplify pull (yes this project will update backend)
• make a change to auth (I changed the redirect urls)
• amplify push

Expected behavior push should work/update as with the original project

Desktop (please complete the following information):

• OS: Mac
• Node Version. v13.5.0

Additional context Missing following section from team-provider.info file:

"categories": {
            "auth": {
                "roarapp630360af": {
                    "hostedUIProviderCreds": "[{\"ProviderName\":\"Facebook\",\"client_id\":\"xxxxxxxxxxxxxxx\",\"client_secret\":\"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"},{\"ProviderName\":\"Google\",\"client_id\":\"xxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com\",\"client_secret\":\"xxxxxxxxxxxxxxxxxxxxxxxx\"}]"
                }
            }
        }

Adding the section fixes the issue

[skarensmoll]

Any news on this issue? I’ve got the same problem.

[amuresia]

+1, it’s happening in 4.36.2