Blank (white screen) after Navigate() on iPad

[maskwer]

Hey,

I have a screen with multiple controls, which functioned properly a few weeks ago. Now, after navigating the iPad shows a white screen after. The strangest thing is on Android everything works properly.

What I already tried is:

- copy the whole screen in PA studio; after few minutes of loading the sessions times out (?)

- export and import of the whole app

- optimize the screen with gallery controls for repeated controls

- debug with monitor, which is loading every single piece of code until Navigate(), here is the point where the app stops working showing the white screen

- Navigate() to the screen directly without any code (collections, variables)

- change the development version in studio

- compare the screen complexity; according to the PA studio I have one screen with ~2000 controls, although there is only one gallery and few labels, the affected white screen issued has about 1200 and has a lot of more complexity. How is the studio counting the controls in the reality?

- change the name of the screen

- used both Navigate([@]) and Navigate()

- clear the cache, reinstalling of the PA on iPad

- change the setting in the app itself for loading controls and so on (if I turn it off, the app crashes instantly. the only possibility here is to restore to the last version in admin panel)

I have some other complex applications, which are functioning properly on iPad. I tried to search on the community forum and found out some other members with the same problems in the past, but without a proper solution.

Does anyone have an idea what the problem could be?

[maskwer]

Does really noone knows what the problem is? Didn't noone have the same problem?

[Pro_User_365]

• Hi @maskwer ,

It sounds like you're experiencing a specific issue with PowerApps on iPad, where navigating to a screen results in a blank (white) screen, despite the same functionality working correctly on Android devices. Given the extensive troubleshooting steps you've already taken, including copying the screen, exporting and importing the app, optimizing controls, debugging, direct navigation, changing development versions, analyzing screen complexity, renaming the screen, clearing the cache, and adjusting app settings, the problem seems quite complex.

The issue could be related to platform-specific behavior in PowerApps, especially given the difference in behavior between iPad and Android. The screen complexity and control count might be contributing factors, as you mentioned there's a discrepancy in control count reported by PowerApps Studio. It's possible that the iPad version is having difficulty rendering or processing the screen due to its complexity or a specific control.

• Here are a few additional suggestions you might consider:
• 1. **Test on Different iPads**: If possible, test the app on a different iPad model or iOS version to see if the issue is consistent across different devices.
• 2. **Simplify the Screen**: Temporarily simplify the problematic screen by removing some controls, especially complex ones like galleries, to see if that resolves the issue.
• 3. **Check for Platform-Specific Properties**: Some controls or properties might behave differently on iOS. Review the properties of controls on the problematic screen to ensure they are compatible with iOS.
• 4. **Update PowerApps and iOS**: Ensure that both PowerApps and the iPad's iOS are updated to the latest versions.
• 5. **Seek Support from Microsoft**: If the issue persists, consider reaching out to Microsoft Support for more tailored assistance, as this might be a bug or a platform-specific limitation.
• Since you've already tried many troubleshooting steps, it might also be helpful to replicate the screen from scratch (rather than copying) in case there's a hidden corruption issue.
• Remember, complex PowerApps can sometimes behave unpredictably on different platforms, and it may require some trial and error to identify the exact cause of the issue.

Note: After receiving the answer, if you think it's helpful, please consider accepting it. 😊 Regards! Ali Shahzad

[maskwer]

OK, I found something new. If I play the PowerApp in Edge browser, the white screen issue is happening. With the Chrome browser, not. I tested on 2 PC's with each 8 and 16GB RAM.

[maskwer]

The Edge console showing the following error after navigating to the affected screen:

Uncaught RangeError: Maximum call stack size exceeded

[Pro_User_365]

@maskwer ,

Based on your client's new information about the white screen issue occurring in the Edge browser but not in Chrome, and considering the error message in the Edge console, it seems the problem is browser-specific rather than an issue with the PowerApp itself. Here are some steps to troubleshoot this:

1. Browser Compatibility: PowerApps may have compatibility issues with certain browsers. Check if the Edge version used is supported by PowerApps.

2. Browser Settings and Extensions: Sometimes, browser settings or extensions can interfere with PowerApps. Try resetting Edge to its default settings or running it in incognito mode to rule out these factors.

3. Inspect Edge Console Error: The specific error message in the Edge console could provide insights. Research the error or share it with Microsoft support for detailed analysis.

4. Update Edge: Ensure that the Edge browser is updated to the latest version, as updates often resolve compatibility and performance issues.

5. Cross-Browser Testing: Since it works in Chrome, test the PowerApp in other browsers (like Firefox or Safari) to determine if the issue is isolated to Edge.

6. Contact Microsoft Support: If the issue persists, it would be advisable to contact Microsoft Support with details of the error message and the behavior across different browsers.

Remember, browser-specific issues can be tricky, and sometimes the solution lies in a simple update or configuration change.