Christopher Robert

After many many many frustrating hours trying everything I could find to resolve the issue described here, I finally got my env back up by following a modified version of...

However: after all this, I went back to Amplify Studio, and none of the "Manage content" functionality was working. The drop-down has my tables, but they show no content in...

This is what fixed my Amplify Studio Data Manager: 1. amplify env checkout BRANCH 2. amplify api gql-compile --force 3. amplify push -y Honestly, this whole experience has been a...

> To everyone in this thread, you can simply update the expiration date for your expired keys if you aren't rotating them. > > Go to your AppSync API in...

Your proposals sound very sensible to me! I would only add: 6. When not mutually-exclusive in a logical or functional way, appearances can be combined by listing them in a...

I meant that we might hope that users wouldn't specify mutually-exclusive appearances, but if they do, we could have a well-defined behavior. In such a case, I could see either...

Well, there's a real tension between wanting the appearances to be somewhat client-specific and then wanting to validate them at server/upload/validation-time. In practice, the upload/validation process has tended to be...

From a user perspective, immediate-clearing can be a total nightmare. For example, take an informed-consent question, upon which 1,000 later questions are hinged (the whole survey ends vs. proceeds). In...