Kethan sai

Hello @miguelflores1993, Thank you for reaching out. I was able to replicate the behaviour in amplify application. In order to replicate the message I performed the following steps. I am...

Hello @miguelflores1993, on reaching out to the team and confirming the behavior. Currently, amplify-cli currently does not support importing resources across regions. If your staging and prod environments are in...

Hey @miguelflores1993, Thank you for the information. I replicated the following by utilizing the following steps. 1. In my dev environment I ran `amplify import auth`. 2. ran `amplify push`...

Hey @JoakimMellonn, thank you for reaching. Could you let us know the openssl version currently installed by running `openssl version`. Additionally, could you try directly running the openssl command in...

@JoakimMellonnThe terminal should prompt you for a pass if we remove the `-passin` but we can simply press return without any input if the cert does not have a password...

Hey @JoakimMellonn, thank you for the information. I was able to reproduce the issue using `OpenSSL 3.1.1 30 May 2023`. When I switch to `LibreSSL 3.3.6` the error does not...

@JoakimMellonn reopening the issue for tracking this behaviour and provide better error messaging.

Hey @ymentha14, thank you for reaching out. I was able to reproduce the issue from the provided reproduction steps. Marking this as bug. If the intention is to remove the...

was able to consistently reproduce this issue using Amplify studio with the following steps 1. select authentication 2. remove `email` and add `phone number` as login mechanism 3. add `social...

Note: further testing on CLI. using add auth headless with `-----BEGIN PRIVATE KEY-----`, `-----END PRIVATE KEY-----` causes the hosted provider function to fail. ran: `cat authadd.json | jq -c |...