bergmorten
bergmorten
I do nothing special in the auth flow, and It works perfectly for desktop logins. It seems to related to Androids mobiles not just OxygenOS. If you have a sample...
An update: I upgraded to the latest aws-amplify today (6.0.28), and it seems to work better. Still, there is some CPU usage when doing the authentication, but it's much better....
I think that would be a good solutions. It seems that way encryption keys / BigInt are generated today use a lot of resources.
I just verified my IAM profile and I'm member of admin group, and the policy of `AdministratorAccess` and does indeed include `TagResource` in KMS. Could it be that amplify use...
Thanks I'll try this :-)
@ykethan An delayed update ( took a few day off last week). First I tried to add inline policy for my IAM account: ``` { "Version": "2012-10-17", "Statement": [ {...
Very odd, I see that you have kms:* , while I only set kms:TagResource and kms:UnTagResource. Must I do re-login for the policy to be effective? Still I think it...
I got the aws-amplify-console to push the custom CDK, the error I had previously with console was not a tag resource error 👍 Since I now have pushed the CDK,...
@ykethan I do confirm that this did work. I did checkout of an another environment, which did not yet had custom backup pushed. Then updated my amplify -> aws profile...
Any update of this. Has the website been updated or must we still enter user branch as environment variable?