John Corser

Did you previously override cloudformation configuration directly?

You may need to `ampify update api` to remove the dependencies before removing auth, then set them back again after.

Unfortunately, it looks like this could be some messy manual work. I don't like this answer, but right now the only way is to remove auth from every resource in...

Side note, the provided Vagrant solution also has problems: ``` vagrant@ubuntu-xenial:/vagrant$ stack setup Could not parse '/vagrant/stack.yaml': AesonException "failed to parse field 'extra-deps': (Invalid package identifier: \"semigroupoids-5.0.1@rev:0\",\"semigroupoids-5.0.1@rev:0\")" See https://github.com/commercialhaskell/stack/blob/release/doc/yaml_configuration.md. ```

Fixed in vagrant by upgrading the stack binary using ``` curl -sSL https://get.haskellstack.org/ | sh -s - -f stack upgrade cd /vagrant stack setup stack build stack exec hue-dashboard ```...

It looks like you can upvote this feature request: https://github.com/LedgerHQ/ledger-live-desktop/discussions/4005 My assumption is when it gets implemented in desktop it will also work in mobile? In the meantime you can...

Customers in https://github.com/aws-amplify/amplify-cli/issues/9532 are reporting downgrade to CLI v7.6.8 works around this issue

Can you please share your user pool configuration? Also your `cli-inputs.json` contents?

We are having a lot of trouble reproducing this internally. We have tried creating various configurations on various previous versions of the cli, then upgrading and trying to push something...

I am particularly interested in the `requiredAttributes` of your generated cloudformation - especially if there are discrepancies between those and what's in cli-inputs.json. https://github.com/aws-amplify/amplify-cli/pull/9251 changed the behavior around that and...