Please be so kind as to read the full post before responding.
Thank you for your consideration.
Do you mean that your app works well within PowerApps Studio Editor rather than WebPlayer and your Mobile device?
For your first question, currently, I could not reproduce your issue on my side. You could consider take a try reduce the amount of controls within your app, then re-publish your app, run your app in Web Player/Mobile device again, check if the issue is solved.
I think this issue may be related to the amount of controls added in your app. The more controls you add, the more generation time your PowerApps app needs.
In addition, please make sure you have enough RAM to run your app. Please close other processes within your computer and your Mobile device, check if the issue is solved.
For your second question, currently, there is no exact limit in the amount of controls added within a PowerApps app. The recommandation is that do not add more than 500 controls to the same app. Please check the following article for more details:
For your third question, currently, there is no available diff tool to compare different versions of an app in PowerApps currently.
The technical requirements for PowerApps are here :- https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/limits-and-config
Yes, I mean that my PowerApp works well and without errors in PowerApps Studio.
It does not work at all in the WebPlayer, the PowerApps for Windows App, or PowerApps on Android.
Yes, this particular PowerApp is really big and complicated with easily 700+ controls.
Just for a test, I have copied the PowerApp and removed 30 data cards containing around 300 controls.
The smaller copy works everywhere again.
It does not - that is my point - The title inclues the word "Limits" but there are no words on Limits other than "Request Limits". I would have expected some words about maximum number of Screens, Controls, Collections (although the latter might be tricky - it will depend upon the lentgh of a record in each collection) and variables.
But they are not there, nor any guidance. A PowerApp might work on a Laptop, but might not work on a mobile (cell) phone because the amount of avaiable memry is less.
We are actively looking into the issue you are facing, however cannot yet track down to the root cause with the sessionIds you provided. Can you give us permission to access your app for further investigation? You can reply to me email@example.com with your permission or locally saved app.
One of the biggest paradigm shifts for reducing the number of controls in your app (aka: Improving Performance) is to use Variables (or Tables, or Collections) and Galleries.
I would 100% recommend reading Mehdi's performance blog post and focus on the last section where he mentions this method.
There is also quite an in-depth forum post here in the community on the subject. Incorporating this can significantly reduce the number of controls in your app thus increasing performance.
I sent you an email about this issue with more details on the PowerApp in question and with permission.
But, I have not yet seen any reaction yet.
Did the email arrive?
Tanks a lot,
Check out new user group experience and if you are a leader please create your group
Did you miss the call?? Check out the Power Apps Community Call here!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.