Answered

PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

Like (1) Share

Report

Posted on 7 Oct 2019 05:44:57 by fptkiller

Hi all,

After updating the PowerApps to the latest version on iPad, I am having an issue that the PowerApps keeps quiting to the home screen unexpectedly after 1 hour on-screen.

I haven't experienced this issue at all on the old versions but since the version 3.19093.16, it starts to happen. I also tested the app on different iPad models (iPad Air 2, gen 5, gen 6) to see whether the issue is from the device itself or the app but the issue persists on all of those models.

The session ID: f826faf7-acae-4ef4-900e-d01216fe5d9c.

Is there anyone experiencing the same issue on iPad?

Kind regards,
DP

Categories:

General Questions

All responses (10)

Answers (1)

jurivera 33 on 10 Oct 2019 at 16:58:35

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

CONFIRMED!!

I updated the Powerapps App inthe iStore and its been now up for about 4 hours.

Thanks everyone!!
fptkiller 11 on 10 Oct 2019 at 03:24:46

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

Confirmed. It's stable since I updated to the latest version of PowerApps.
Verified answer

Luke-AO 16 on 09 Oct 2019 at 23:27:42

Like (2)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

6 of our 7 info kiosk IPads have updated to PowerApps version 3.19095.18 and have been stable since. Try updating to the latest version and see if this resolve for all.
jurivera 33 on 09 Oct 2019 at 19:35:03

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

I thought so too, but when I run the app on Chrome on Windows 10, it works like a charm. No problems there.
It could be the Powerapps iTunes app the culprit.
fptkiller 11 on 09 Oct 2019 at 00:22:30

Like (1)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

I believe that the issue comes from the PowerApps itself, not either iPad os or iPad models. I checked on an iPad gen 6 running the iOS 12.3.1, and the issue occurrs too.

I notice that the issue appears after updating to the PowerApps version 3.19093.15 and now 3.19093.16.

Hope PowerApps team will fix this issue as soon as possible.
Luke-AO 16 on 08 Oct 2019 at 22:42:59

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

@jurivera we have 7 iPads used as info kiosks and they all have the same issue
jurivera 33 on 08 Oct 2019 at 15:32:31

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

Yep,

That is whats happening to me too. Sorry for the confusion.
Luke-AO 16 on 08 Oct 2019 at 05:03:44

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

I am also having the same issue but the app quits to the "My Apps" menu, not the iPad home screen. This appeared to start when IOS updated to iPad OS 13
jurivera 33 on 07 Oct 2019 at 20:01:36

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

Just Updated to latest version 13.1.2 and restarted the Ipad.
Still got the same result.

I now just turned the unit completly off and on again (standard procedure) and I'm leaving it on in the app I created (a survey app).
I will verify within the hour to see if it went down Again.

Side note: I had my other iPad (iPad Pro 12", latest OS version) and decided to do the same setup to discard that the unit was faulty, but this time it stopped after two hours. what was weird was that when I start the app within Powerapps again, it showed me a green bar at the bottom stating it just reconected (to Wifi, I presume). Could this be caused by an intermittent wifi conection?

I'll keep you posted.
jurivera 33 on 07 Oct 2019 at 17:24:29

Like (0)

Report

Re: PowerApps quits unexpectedly to the iPad's home screen after 1-hour onscreen.

Yep,

I have the same problem.
My version was on 12. something (can't remember).
I'm running an update to see if that solves the problem (bringing up to 13.1.2).

I'll post later and let you know how it went.