bergmorten

Yes, and I think the new design of the new amplify console is much less intuit. And still there is no button for manual build, you must enable CI and...

upvote, we need a button in the amplify console UI which trigger a new build when CI is turned off.

Update `identifyUser` in package `aws-amplify/in-app-messaging` has all we need, except that channel is locked to `CHANNEL_TYPE` which is `IN_APP`

We need a function to add FCM/GCM tokens in order to send push messages. We do not want to use the in app messages because it is not supported in...

I've used the workaround and not tried to deploy without it. If two deployments/apps use the same backend then corruption will occur. I think this was a major bug, and...

~~I've also problem with this. When getting 3.556.0 I get `AwsSdkSigV4Signer is not a constructor`. AwsSdkSigV4Signer is not a class constructor in the latest releases?~~ UPDATE: I think my issues...

Update. I manage to set cli version to 12.11.1 (there was still a `_LIVE_UPDATES` entry for my branch which overwrite the global build setting). I think it is very odd...

Another update. I then deleted the created backend environment and did a redeploy with amplify cli 12.11.0 and it worked :-) I do not know if the issue was with...

What I think happen was that even when preBuild phase was failing the amplify-cli created an empty backend environment. So when preBuild phase was fixed and it did checkout an...

We need also this option. I think the best approach is to make it equal to the hdf5 specification, e.g. `set_scale`, `attach_scale` and `detach_scale`: https://docs.hdfgroup.org/hdf5/develop/group___h5_d_s.html example: https://docs.hdfgroup.org/archive/support/HDF5/Tutor/h5dimscale.html