Power Platform Community Forum Thread Details

Hello, Community,

I’m having trouble opening an app in edit mode on Power Apps Studio and would appreciate any guidance on resolving this.

Problem Details:

Description: When launching the app in edit mode, it just keeps loading indefinitely, showing only a loading screen with no error messages – it’s stuck in an infinite loading state. The app functions correctly in the latest published production version, but I’m unable to access it to make any edits.
App Scenario: The app is used for corporate travel requests and includes connections to SharePoint lists, Excel files, and Power Automate flows.
Environment: Production environment; Canvas App, tablet mode, used exclusively on desktop PCs.
Recent Changes: The last person to edit the app duplicated a screen, and that same day, it took over 10 minutes to load in edit mode. Since then, they have not been able to access the app in edit mode again.
Troubleshooting Steps Taken:
- Cleared browser cache
- Switched to a different browser
- Tried incognito mode in various browsers
- Tested with an Admin user and other users (none could access edit mode)
- This is the only app that cannot be opened in edit mode
- With skipAutoRefresh and blocked connections, the download size exceeds 600MB and continues growing
- Restoring a previous version is not feasible, as it would lose significant modifications and risk disrupting the production app.

Additional Information:

Connections and Data Sources: The app connects to SharePoint lists, Excel files, and uses Power Automate flows (No SqL, No Dataverse)
My last inspection of the app revealed a large number of controls per screen and cross-screen control references. However, we’re unable to access edit mode to fix these issues.
We’ve been experiencing this issue for 2 weeks

I’d appreciate any suggestions or solutions you could offer. Thanks in advance for your help!

Categories:

General Questions

I had a similar experience with an app that wouldn’t load in edit mode, and the only viable solution was to load a previous version in a test environment. From there, I followed these steps in this order and managed to resolve the issue:

I restored an earlier version of the app in a test environment. This allowed me to investigate without affecting production and understand if recent changes were causing the issue.
Instead of duplicating entire screens (which, in my experience, tends to bring problematic cross-references), I rebuilt complex screens from scratch, removing unnecessary dependencies.
I temporarily disabled some data source connections and Power Automate flows that weren’t essential for loading the app. This helped reduce the initial load and identify if any particular connection was causing the issue.
I considered breaking down the app into modular components or sub-apps. Separating functionality into smaller modules simplified the structure and improved overall performance.

I hope this approach is helpful and that you’re able to resolve the issue by following these steps.