Harsh

@Robuske I started looking into the issue and found that the only event missing from publisher is `Amplify.configured`. I tested others and seems to be working fine. ``` Listener received: ...

Thank you for replying. I'll keep the issue opened for one event that is not being fired.

Would you be able to share you code snippet that is being used upon device getting awaked. Additionally, could you also share the metrics that you are seeing, if there...

@tobias-feldmann Do you think you would be able to get verbose logs for the scenario that you faced? You can enable verbose logging to the console by doing this before...

@tobias-feldmann @kparichan Are you guys still facing this issue?

> If it is invalid, we rely on the backend to reject it when making our API call. What do you do if the backend rejects it? Do you sign...

I think in your case, after the device wakes up after a while, does the app actually restart because it feels you need to call `Amplify.configure` again. Because I see...

> Amplify.AuthError error 1 This is a configuration error. Thats why I believe there is some sort of timing issue between the `fetchAuthSesssion` vs `Amplify.configure`, as I guess the app...

Cool.. For now I am gonna close the issue, please feel free to open another issue if you are seeing issues that are not recoverable.

Can you please provide detailed analysis to the team so that we can investigate further (as also requested above)? * Code snippets * Reports that you recieved * Claims that...