Unanswered

App crash / reload loop on mobile

(0) Share

Report

Posted on by SynergyM

I'm developing a dashboard application that connects to an Azure SQL database both directly and via Microsoft Flow. It's fairly complicated with hundreds of controls. It works well in Chrome and in Edge on my Windows 10 Surface Pro 4. Chrome eats up 1.5 GB of RAM when it's running.

It used to work on my iPhone X as well. At some point it stopped working on the iPhone around a month ago. I'm not sure if it was a change I made to the app, or an update to PowerApps that broke it. Essentially the app opens on mobile, starts the data loading process, and before all the data loads into the galleries, the app crashes and the loading process starts over. I've let it crash loop for a half hour before to see if it would eventually work, but it does not. I don't necessarily need the app to run on an iPhone X, but I do need it to run on an iPad. Unfortunately I don't have an iPad for testing; only the iPhone.

Here's what I've tried so far:

Signed out of PowerApps on my phone and signed back in.
Removed PowerApps from my phone and reinstalled it.
Cut / pasted several galleries, rebuilt the date picker control, then republished the app.

Here's a crashed session ID from the iPhone:

2ecc298c-76ed-4ed8-bbba-1d504440b908

Any suggestions?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

cherie on at

Like (0)

Report

I took a look at your session and it looks like the reload loop issue is due to running out of memory on the device.

Do you know what changes you made to the app?

How many galleries do you have in the app? Can you try make an app with just one of your galleries and see if it happens?

Was this reply helpful? Yes No
SynergyM 81 on at

Like (0)

Report

That's actually really helpful, thank you. I've added several galleries since then, so that makes sense. There's probably 15 galleries on the screen(Around 5 visible at once).

The app is a dashboard that lets the user switch between 3 warehouses, and I did recently make a change to optimize how quickly we could switch between them. There's a button for each warehouse at the bottom of the screen. The OnSelect property is something simple like this: UpdateContext({warehouse: 3}). There's a "duplicate" gallery for each market that has the Visible property set to something like warehouse=3. Each gallery Items property is set to something like Filter(allSupp, WH=3).

Before I made the change, I didn't have galleries for each warehouse. I filtered the data in the gallery Items like Filter(allSupp, WH=warehouse), and there was fairly long delay when clicking the buttons to switch between warehouses. I remember that version of the app running on my phone, so it must have used up less memory. The new method with hidden galleries is 2-3x faster. It still takes about 2.5 seconds to switch, so maybe I can find a better way.

So it sounds like I've gained performance by caching my galleries in memory, but maybe I should find a different way to improve performance?

Was this reply helpful? Yes No
cherie on at

Like (0)

Report

Can you try turning on some of our experimental features (if they are not on) to see if they help?

In particular, Control property optimization and Delayed Load.

You can find these in App Settings -> Advanced Settings

Was this reply helpful? Yes No