Older versions of application open on iPad fine. Since version 3.18061.12, powerapps loads fine, but the actual application I am building just hangs at the "opening" screen
Solved! Go to Solution.
After you re-saved, did you also publish the newly saved version?
Can you provide an updated session id as well?
Please provide a tutorial on how to setup Fiddler and perform such a trace. I cannot find PowerApps debugging information anywhere in the documentation. This is a must, especially if you are asking for if from Users.
With "low-code apps", you (microsoft) own all the code and the bugs. If we need to quickly help find what is wrong, we need the tools to do so. I'm preparing to deploy a single PowerApp for daily use to ~700 people within my org.
Is PowerApps ready for prime time?
These types of "unkown errors" and "slow downs" cause me great concern.
The community needs you to show us how to debug these apps effectively and where to report issues when they do arise. Will you help us?
Here is a link to documentation on capturing traffic with Fiddler on iOS: http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureForiOS
I understand your concerns. When you encounter issues, you can report them on the community forum which is actively monitored or through other support channels you may have to PowerApps.
Its very difficult for me to consider "posting an issue to the forum" as an enterprise-level form of support. Especially for mission-critical applications.
We are more than happy as an org deploying PowerApps to debug, triage, and FORMALLY submit tickets through a process that Microsoft establishes, but submitting to a forum feels a bit "black box" (the request goes in, who knows when or what comes out).
I hope you don't take this the wrong way. I'm not trolling by any means. I've been evangelizing your product with my (fortune 100) organization and actively developing apps. We're at the point now where these apps are about to hit hundreds and thousands of internal users. To pass issues to the forum isn't a typical method of enterprise support.
It may be that I'm just not used to the method. I'm active on the forums already and know the high caliber of responses, just nervous about relying on this method for critical support.
We have created a support ticket to root cause the issue; engineering investigative work is still in progress. Thank you for your patience.
@ericonline, can you send me an email: faisalil at microsoft.com. I want to help debug this issue. The info that we have so far is not enough to provide a fix.
Another thing, PowerApps does provide a way to open support tickets (entriprise level support) outside the fourm and using that, you can talk with our support team and get issues to engineers ASAP. Also, its worth mentioning that we also monitor the fourm as much as we can.
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.