InnovateWithEric
InnovateWithEric
Confirmed that it works on Monteray and other os, just not on Ventura
@Kilo-Loco - can you reply to @lazpavel comment on 7/18? The symptom `"Error: File at path: '/Users/kiloloco/local/tmp/latestr-amp/amplify/cli.json' does not exist"` is consistent with the known issue we're fixing for https://github.com/aws-amplify/amplify-cli/issues/10686...
The fix here is to improve the error message from amplify export to message that export of imported auth is not supported.
@bc4253 - did you try the step in this message above: https://github.com/aws-amplify/amplify-cli/issues/10193#issuecomment-1132433956 ? Does that fix for you?
@josefaidt to confirm if still an issue with current tutorial and CLI
We don't explicitly support this use case. It is possible that an approach of explicitly denying CloudFormation could have the desired effect, but it would be on the customer to...
I believe I understand because I saw a similar situation. They're alerting because they see a reference in your repo to a package name in which they found malware in...
I believe I understand because I saw a similar situation. They're alerting because they see a reference in your repo to a package name in which they found malware in...
I believe I understand because I saw a similar situation. They're alerting because they see a reference to a package name in which they found malware. In this case, the...
The `Invalid feature flag (FF) configuration` is happening because an older version of Amplify is seeing an unknown feature flag (which has come from a newer version of CLI) and...