Roman Naumenko
Roman Naumenko
I've ended up swapping appRoot with front-end ``` version: 1 applications: - appRoot: cof-website
Wanted to add to the list of checkout griefs The checkouts of front-end is even more complicated with dedicated environments in separated accounts 1. the amplify env checkout doesn't work...
Here's app-id for dev: d2bgfp3zb4o7c8
I hope the endpoint is simply not documented yet, nope - API blocks access for API keys ``` { "message": "Your request to GET /v1/threads must be made with a...
Didn't they retire `amplifyPush` script? https://github.com/aws-amplify/amplify-hosting/blob/main/scripts/amplifyPush.sh
> A potential workaround to autoSignIn on another tab might be to setup a storage event listener that checks if the cognito access, id, and/or refresh tokens have been stored...
> This blog hints at combining Magic Links with the verification flow to achieve this. I haven't tried it myself, but it sounds interesting. https://www.zeile7.de/insight/user-authentication-with-aws-cognito/ This is great write up...
Still a bug in 12.10.0
@mgamsjager did you ever figure it out? This would be very helpful to reviewing changes in generated CF templates.
Thanks, @reesscot Indeed, I've added messing component in Amplify backends and error is gone. Does the package allow message removal programmatically from event notifications? Or there is always interaction from...