'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Recover a Power Apps Canvas App After Screens Disappear in Azure DevOps
Question details
The user needs to recover the design interface of a Canvas Power App after screens and controls vanished following a publish and commit to an Azure DevOps repository.
- Product
- Power Apps
- Device & OS
- not provided
- Scenario
- Publishing and committing changes in a Canvas Power App connected to an Azure repository.
- Observed behavior
- Screens and controls disappeared in the editor, although the published app still functions in Play mode. Branching and merging failed to restore the missing design elements.
Ensure you have gathered all relevant repository history, including recent commits, branches, and the specific application details, before reaching out for specialized support.
Report the Migration Issue to Azure DevOps Support
Since this is a complex integration and migration issue between Power Apps and Azure DevOps, engaging specialized support is the most effective path to recovery.
When a Canvas app loses its screens in the editor but continues to work in Play mode, it indicates a desynchronization or corruption in the source files during the commit process. Because standard branching and merging do not resolve this, the issue requires intervention from the platform's support team.
Collect your Azure repository history, recent commits, active branches, and the specific Canvas app name or ID that is experiencing the missing screens issue.
Go to the official Azure DevOps support and feedback channel via the Microsoft support portal.
Create a support request describing how the screens and controls disappeared after publishing and committing, making sure to note that the app still functions in Play mode.
Boost Your Productivity with WPS Office
While specialized platforms handle custom app development, WPS Office provides a reliable, lightweight, and free solution for your everyday document, spreadsheet, and presentation needs. It ensures seamless collaboration without the complexity of advanced developer tools.
- 1. Download WPS Office: Visit the official WPS website and click the free download button for your operating system.
- 2. Install the software: Run the downloaded installer and follow the straightforward on-screen instructions to set up the suite.
- 3. Open existing documents: Launch WPS Office and open your existing Microsoft Office files with full compatibility.
Frequently Asked Questions
Why does my Canvas app still work in Play mode if the screens are missing in the editor?
The published version of the app runs from a compiled state that was saved to the server before the editor files were corrupted or desynced during the Azure DevOps commit process.
Can I revert to a previous version of the app within Power Apps?
Yes, you can check the Version history in Power Apps by selecting the app, clicking Details, and navigating to the Versions tab to see if an older, intact version can be restored directly.
Does branching and merging in Azure DevOps fix lost Canvas app controls?
In this specific desynchronization scenario, branching and merging often fail to restore the design because the underlying source files representing the screens were likely overwritten or improperly synced during the initial commit.
