aws-amplify / aws-amplify/amplify-cli
Added Sign in with apple, Having error HostedUIProvidersCustomResourceInputs (Custom::LambdaCallout) while Amplify Push
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### How did you install the Amplify CLI?
curl
### If applicable, what version of Node.js are you using?
v19.1.0
### Amplify CLI Version
10.5.1
### What operating system are you using?
Mac Ventura 13.0.1
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
### Amplify Categories
auth
### Amplify Commands
push
### Describe the bug
1. Updating auth via `amplify update auth`
Followed the steps mentioned in the reproduction steps.
2. Applying change to cloud via `amplify push`
Facing Error over here:

Cloud watch logs:
```
INFO InternalErrorException: Internal server error.
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
```
```
{
"Status": "FAILED",
"Reason": "See the details in CloudWatch Log Stream: ******",
"PhysicalResourceId": "2022/12/02/[$LATEST]*****",
"StackId": "****",
"RequestId": "7550d102-29fc-4377-b31d-d5759f845fbd",
"LogicalResourceId": "HostedUIProvidersCustomResourceInputs",
"NoEcho": false,
"Data": {
"err": {
"message": "Internal server error.",
"code": "InternalErrorException",
"time": "2022-12-02T10:12:13.234Z",
"requestId": "dbc******",
"statusCode": 500,
"retryable": true
}
}
}
```
### Expected behavior
I want to configure Sign in with Apple - OAuth social providers using amplify cli.
### Reproduction steps
1. Updating auth via `amplify update auth`
- What do you want to do? Update OAuth social providers
- Select the identity providers you want to configure for your user pool: Google, Sign in with Apple
- Enter your Google Web Client ID for your OAuth flow: ****
- Enter your Google Web Client Secret for your OAuth flow: ***
- Enter your Services ID for your OAuth flow: com.myapp.myapp.sid
- Enter your Team ID for your OAuth flow: ****
- Enter your Key ID for your OAuth flow: ****
- Enter your Private Key for your OAuth flow: *****
**Note:** For the Private key I am entering key from .p8 file by removing `-----BEGIN PRIVATE KEY-----`, `-----END PRIVATE KEY-----`, \n, space at the end of line and pasting main private key in single line. (As mentioned [here](https://github.com/aws-amplify/amplify-cli/issues/11264#issuecomment-1292314175))
2. Applying change to cloud via `amplify push`
Produced error mentioned above
### GraphQL schema(s)
```graphql
# Put schemas below this line
```
### Project Identifier
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
Contributor guide
Research direction
Reproduce the flow with `amplify update auth` followed by `amplify push`, then inspect the `HostedUIProvidersCustomResourceInputs` failure and its CloudWatch logs. Confirm whether configuring Sign in with Apple succeeds without the InternalErrorException and the push completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js, typescript
- Domain
- authentication, cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100