Brian Lenz

Thanks, @josefaidt, and no worries on the delay 👍 I can successfully pull production and `staging` into an empty directory. Everything looks good for both of those in `#current-cloud-backend` and...

@biller-aivy sure! I suspect you've hit the heart of the issue. It looks like that file is corrupted. Do you have any ideas how to fix this? ``` $ unzip...

Thanks, @josefaidt! Right now, the `dev` environment (backend) is _not_ connected to a frontend. The `staging` and production backends are the two environments currently connected to frontends. Thanks for your...

@josefaidt I should mention that at one point the `dev` environment had been connected to a frontend, but we switched things around so that is no longer the case.

Hi @josefaidt! I haven't had a chance yet to try this. I need to go back in our git history to (approximately) the day that we had this issue and...

Super helpful, @josefaidt, thanks! I'll let you know once I have a chance to work on this 👍 > Great callout, and yes, there is a known instance we are...

We experienced the same issue in trying to set up front end hosting (Next.js) for our existing backend. We have a monorepo with the `appRoot` set to `web` in the...

Hi @josefaidt! It's possible documentation can be improved, but was there an intentional, breaking change from Amplify CLI `9.1.0` to the current Amplify CLI version? The behavior has changed, which...

@josefaidt, thanks much for the quick response! We don't do any automated backend builds or pushes (we have **Enable full-stack continuous deployments (CI/CD)** turned _off_). We have an Amplify backend...

I just found these two issues, which seem to be for the same thing: https://github.com/graphql-compose/graphql-compose-mongoose/issues/376 https://github.com/graphql-compose/graphql-compose-mongoose/issues/377 Looking at the tests now...