Aaron S.

This looks good. Thank you for making this change! I'm bringing the branch up to current now and will merge this in when the tests finish running.

Merged. Thanks again for the contribution!

A quick attempt to reproduce didn't work. I have a guess, but would need to see more of your project to validate. The function `getCategoryName` is only part of the...

Reconnection is now staged on the `next` tag in preparation for release in aws-amplify v5. To test against this update install the `next` tag version of the aws-amplify packages your...

Hello, I've been troubleshooting this issue yesterday and today. I have a [tested fix out for PR](https://github.com/aws-amplify/amplify-js/pull/10353). I had attempted to resolve this in a [prior change](https://github.com/aws-amplify/amplify-js/pull/10298) that solved for...

The fix has been merged and will be available on the `unstable` tag shortly. The full release that you can auto-upgrade is expected to be out a week from tomorrow.

Timestamp can be one word or two. The error from the related issue is what matters. I just tried to trace out the API interface that needs this to be...

Maybe things have changed since this issue was create, this request sounds a lot like the [list behavior](https://docs.amplify.aws/lib/storage/list/q/platform/js/). Is there a gap between what your looking for and what this...

Thank you for the great detail. I have been able to reproduce this issue and have a change in PR that fixes the issue in the example app I'm testing...

As mentioned above, I have been able to reproduce this issue. In testing out the above fix, I thought my testing of the fix was still failing due to issues...