PDF Experimental Causes This app closed unexpectedly

(1) Share

Report

Posted on by wolfcat

So I'm generating a PDF from a gallery that (for this instance) has 128 records.

I get the error message:

"This app closed unexpectedly

This may be because of device memory pressure. Try closing other apps and clearing your cache. If this problem continues, contact your app developer."

I was able to patch into my SharePoint library and once it got to the part of creating the PDFBlob, then using Outlook to send the Blob, that's when it crashes and errors out.

I am able to do this on PC (microsoft store - running powerapps) or the web version, just not on a mobile device.

Categories:

Error handling

I have the same question (0)

All responses (3)

Answers (0)

sohilbhalla 72 on at

Like (0)

Report
Copy link

Link copied!

Hi @wolfcat , I have the same problem with my app which uses the barcode scanner control at multiple places. My App is not crashing while using the app but let's say I used the app and moved it to the background and then later let's say after 5 6 hours if I try to bring the app from the background to the foreground, I get this message and I am on the home page of the app. This is only happening in IOS and very rarely. Did you get any pointers to fix this?

Was this reply helpful? Yes No
wolfcat 60 on at

Like (0)

Report
Copy link

Link copied!

I stopped using the pdf. Too many issues... I'm now using htmltext, with the images, I am using upload.io. So when our user creates a report, it shows up as an html page. Then with html code, I'm able to utilize page breaks. They would then print (save to pdf) and use that. Maybe someday...but the Experimental PDF is anything but easy to use.

Was this reply helpful? Yes No
sohilbhalla 72 on at

Like (0)

Report
Copy link

Link copied!

Here is the official response received from Microsoft

Issue:
The app Closed Unexpectedly

Resolution:
As we checked internally so here iOS Web Views are governed by the settings defined in Apple's Safari Browser, which by default has Intelligent Tracking Prevention (ITP) enabled and 3rd Party Cookies blocked. This means that any attempts to re-login the user silently might fail since cookies are dropped or their access prevented by ITP.

This security mechanisms are implemented on Safari, Braver and soon Chromium based Browsers (Edge and Chrome), since issuing refresh tokens via Browsers is considered a security concern. Cross-Site Scripting attacks can steal refresh tokens and use them until they expire. As a result, the first refresh token issue is only valid 24h (besides the initial token duration) after which the login requires user interaction. This behavior + ITP results in the experience the user is reporting.

At the moment there are no easy solutions for this behavior, silent authentication calls are a best effort scenario and might not be fulfilled. While programmatically (using MSAL libraries) this might be possible, the outcome will always be dictated by the Browser settings.

In short, you can try to uncheck 'Block 3rd Party Cookies" and uncheck 'Prevent Cross Site Tracking' in the Safari Settings, meaning Silent Authentication might go through since access to the Cookies will not be compromised.
https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/isolate-and-troubleshoot-common-issues/troubleshooting-startup-issues?tabs=safari-ios

Was this reply helpful? Yes No