Sporadic black screen after Navigate

[Anonymous]

I am having an issue where directly after navigating back to a screen, the whole app goes black. The only recovery is to exit back into PowerApps itself and restart the app.

The only thing that happens before the Navigate is that i call some APIs to save some data, then the Navigate is called. 

The only thing that should happen after the Navigate in the OnVisible of that screen, is two Set() functions setting the default value in a text field, and one setting a boolean. 

The app is being used in the windows store PowerApps player.

I am at a loss as to what is going on as i have no possibility to debug what happens, i have had Visual Studio debugger attached but no exception seems to trigger, so that was no help, and the code itself is auto generated obviously so couldn't guess anything from that either.

Has anyone experience anything like this?

[v-siky-msft]

Hi @Anonymous ,

Does the issue only happen in window PowerApps player? What about running in the browser or in mobile?

Can you share more detail about the call of APIs? If you remove it, does this issue still happen?

More information is needed to reproduce and resolve your issue.

Best regards,

Sik

[Anonymous]

Hi @v-siky-msft , thank you for replying.

Our customer uses the PowerApps player, and thus we have only been running it using this.

The problem is that the issue is very sporadic and we have been unable to create repro scenario for it, so even if we did test it in a browser, we would have no idea how long to test for to make sure the issue is not present.

Sure, we have a custom connector API that uses an Azure Web App API to save and load filter data. When the user Navigates back from a screen these are saved using the API ( this is where the issue happens ), and when the user navigates to the screen these are loaded from the API. The call to the API finishes as expected with no issue. When the black screen happens its right after the transition animation to the other screen, so you get to briefly see the other screen, then it goes black. Since the calls run synchronously i didnt really consider that these might be the reason for it happening.

We originally used the built in save / load functionality and blamed this, as the issue happened then as well. That is why we implemented the API, and it seemed to be fine for around 4 weeks, at least we got no reports. But just recently  the issue started happening again. We have also tried to publish the app again with no changes to have it built with a new framework release, but this was no help.