"Hot restart" is causing a subsequent call to `Amplify.configure` about amplify-flutter HOT 5 CLOSED

Hi @Rayv1 thanks for bringing this issue to our attention.

Our Amplify Flutter framework currently supports hot reloading but not hot restarting.

For now, we recommend hot reloading or stopping and starting the the app in VSCode. Please let us know if that would be a major problem for you and your workflow.

We will look into how we might fix this issue in the future.

Hi @fjnoyp,

This is a major problem for my workflow - not having the option to hot restart slows me down substantially.

What is the behavior if the app is already configured (in Kotlin / Android), and then the Dart VM is restarted? Do I have to configure it again, or will it work with the previous configuration? Would it be possible to add a separate method here to check if the configuration is initialized already? Why wouldn't we allow configuring it a second time, overwriting the previous configuration? 🤔

from amplify-flutter.

@Rayv1 @fjnoyp Not sure why this was closed, this is a major problem for us, please reopen.

from amplify-flutter.

Hi @Rayv1 thanks for bringing this issue to our attention.

Our Amplify Flutter framework currently supports hot reloading but not hot restarting.

For now, we recommend hot reloading or stopping and starting the the app in VSCode. Please let us know if that would be a major problem for you and your workflow.

We will look into how we might fix this issue in the future.

from amplify-flutter.

Hi @fjnoyp its okay for now. i just comment it out, when using hot restart.

from amplify-flutter.

I put it in a try catch Block, so iam still calling it, but when an error appears, iam doing nothing. The authentication Plugin ist ein still working with this work around.

from amplify-flutter.