Chris Womack

Hey, @Eliav2 and thanks for opening up this issue. I'll mark it as a feature request for now and review it with our team internally, but have a question or...

@Eliav2, appreciate the clarity and reply! I'll review this feature request with the team and we'll update this issue with further questions or updates on progress as they come.

Hello, @ryanmalesic 👋 and thank you for opening this issue. It looks like you're referring to the Gen2 Developer Experience with this feature request. Just to confirm, have you reviewed...

@simonramosb, thank you for opening this issue. Just to confirm, is this a Gen2 app that you're experiencing this in?

@gpavlov2016 and @strickon, you should now be able to verify/test this on `v6.2.0` of Amplify. Can you upgrade to the latest version and let us know if you still experience...

Hey, @jojimcNova 👋. When you state that you're using a custom login page, is it a different URL than what is specified in your config (which is `"http://localhost:3000/"` it looks...

Hello, @mitchh 👋. It indeed is a change from v5 behavior after upgrading to v6 that the `contentDisposition` (as you noted in the docs [here](https://docs.amplify.aws/react/build-a-backend/storage/storage-v5-to-v6-migration-guide/#storageget:~:text=mentioned%20above%3A-,Content%20options,-()). I'll review this with our...

Hello, @brianlenz 👋. While this was opened as a bug, it looks like it's very similar to the feature request in #10393 regarding improved offline session management. Also, the behavior...

Hello, @zahirtanin1397 and sorry to hear you're running into this issue. I'll work on reproducing this error to determine a workaround or if it's a bug. In the mean time,...

@George-field, is there any other or more details on the error message beyond what's in this issue? Also, can you share what version of Java you're currently on as well?...