Caleb Pollman

Suspect the unit test workflow failure [here](https://github.com/aws-amplify/amplify-ui/actions/runs/6897019344/job/18764462312?pr=4644) can be attributed to the example apps pointing to `aws-amplify@latest` ([example](https://github.com/aws-amplify/amplify-ui/blob/ui-react/v2/examples/vue/package.json#L14)). Think we need to audit the versions of Amplify JS we are...

Hi @yuriygavriluk. Have been unable to repro the issue based off the code example you provided. Where are you calling `Amplify.configure`?

To isolate whether the issue may be with the application configuration can you verify that the post sign in redirect is working as expected without the `authenticator` element? Here is...

@yuriygavriluk Totally valid request. Updated the example code [here](https://github.com/aws-amplify/amplify-ui/issues/5048) to conditionally render the sign in/out buttons and provide whether there is a signed in user

@raystorm Thanks for opening this! Need to discuss with the team, will update here once we have next steps

@raystorm Just wanted to update you here, we are aligned with adding the update to `processFile` and will be reviewing your PR. Thanks again for contributing!

@yuriygavriluk Got it. As you were able to repro the issue without using the `authenticator` it seems likely that the issue is in your application setup. Going to route this...

@raystorm We recently made some updates to the `StorageManager` to support new functionality exposed on the `uploadData` API (consumed from `aws-amplify/storage`) used by the component, which has caused some merge...

Hey @raystorm, valid question. Have started reviewing, will finish the review in the next couple days. Thanks for your patience!

Hey @raystorm, there's some problem areas in the upload input resolution we need to sort out in order to correctly address this. Would still like to get this in, but...