Showing results for 
Search instead for 
Did you mean: 
Frequent Visitor

Width of screen corrupted [urgent]

I didn't changed a thing, and few of my screen layouts got completely destroyed, due to some update of Power Apps I suppose...

Width of screen disappeared, and the layout was compressed to some line. After rearranging the proper width, the layout is destroyed, as all other elements inside that screen also have width set to nothing.


This happened to multiple (6) of my screens that contain around 50 elements of each.


Please revert this, as I don't have time to deal with downloading package, changing JSON data and patching the package myself as shown here

My appID: 46ae0a46-0394-4f44-b444-7a1793755672




Frequent Visitor

Hi @Pstork1 - Thank you. I work with bcampbell13 and am working on getting a support ticket submitted for us. I will respond back to you once I have our ticket number.

Frequent Visitor

@Pstork1 - Our (@bcampbell13 and I) ticket number is 25062676. Thank you for agreeing to escalate this for us. 

2104070040005102 - @Pstork1 We now have a powerapps specific ticket number

Resolver I
Resolver I

Did anyone hear an update on their tickets? Mine is still listed as "Open (Troubleshooting)" with no new news since I opened it on 4/6. I have had a check-in email stating that they are still working with it but no real substance.

Frequent Visitor

@BrianCCampbell - went on a Teams call with support yesterday, and it seemed they hadn't heard of this issue before. I explained the issue, and then they requested some screenshots and some log files so they could research it as they didn't know anything. Haven't heard anything back since, but am currently attempting to escalate the ticket, but not fully certain how to do that...

Dual Super User
Dual Super User

Here are some mitigation steps you can try until MS can post a solution.

Steps to Self-Mitigate

Using a Previous Studio Version

Depending on when the user last saved their app, they may be able to use a previous version of the studio to fix their issue.

  1. In the Portal ( ), go to the list of apps. Select the "More commands" button for the affected app and select "Details"


  2. In the versions tab, look at the "Power Apps release" column. Verify that either:
    a. The newest Version of the app has a Power Apps release of 3.21032.0 or lower (eg: 3.21031.0, 3.21025.0, 3.21024.0, etc...)
    b. You are willing to revert to a version of the app that has a release of 3.21032.0 or lower. In this case, select the "More Commands" button for that version of the app and choose "Restore"
    • If neither of the previous two apply, the user must use the ALM tool (see below) or wait for the official fix to roll out.
  3. Navigate to 
  4. Go to Open > Power Apps (Browse Power Apps) > Select the affected app
  5. Select the affected screen in the tree view (it should appear normally).
  6. Switch the properties pane (right side pane) to "Advanced". Check that the Height and Width properties are not blank. If they are, enter these values:
    • For a blank Height, set the formula to Max(App.Height, App.MinScreenHeight).
    • For a blank Width, set the formula to Max(App.Width, App.MinScreenWidth).
  7. Save the app.

The app can now be opened in the latest version of the studio.

Using the ALM tool

This guide assumes that the user has never used the ALM tool (PowerApps-Lanuage-Tooling). If they have, skip to step 5.

  1. Download the ALM tool from the github repository as a zip file  and unpack to the Downloads folder.




  2. Download and install the .NET Core SDK 3.1 .
  3. Open a command prompt and navigate to the extracted folder.
    • Eg: the command is cd C:\Users\bryue\Downloads\PowerApps-Language-Tooling-master for my downloads folder
  4. Run the command .\build.cmd. The command prompt will show "Build succeeded" when complete.
    • Keep this command prompt open for later.


  5. Export the affected app. Due to the nature of this issue, users cannot use "Save as" in the studio and must export a "known good" version of the app via the portal.
    a. In the Portal ( ), go to the list of apps. Select the "More commands" button for the affected app and select "Details"


    b. Switch to the versions tab. Select a known good version of the app and select "Restore". Note that any version of the app that was saved or auto-saved while the issue is present should NOT be used. At this point, DO NOT open the app in the studio.
    c. Now select "Export package" for the app.
    d. Give the package any name you'd like and select "Export" in the bottom-right corner. The package will be downloaded to your computer.
  6. Extract the downloaded .zip file
  7. Find the .msapp file in the extracted package. You should be able to type .msapp in the search bar.


  8. Copy the file to your Downloads folder and rename it to something a little more convenient, eg: BrokenApp.msapp
  9. In the command prompt window run the following command, replacing <Username>:
    • .\bin\Debug\PASopa\PASopa.exe -unpack C:\Users\<Username>\Downloads\BrokenApp.msapp
    • This will create a folder called BrokenApp_src in your Downloads.
  10. In File Explorer, navigate to BrokenApp_src\Src\ (components will be in the Components folder) and open the file with the name of the affected screen.
    • If prompted, open the file with Notepad (any text editor will work).
  11. Near the very top of the file are the properties for the Screen. Look for lines containing Width: = or Height: = and delete those lines. Note: Only delete the lines directly under Screen1 as Screen:.
    • Example: Before and after

Screen1 as Screen:    BackgroundImage: ='Background'    Width: =    Height: =    Fill: =    OnVisible: |-        =UpdateContext({now: Now()});Screen1 as Screen:    BackgroundImage: ='Background'    Fill: =    OnVisible: |-        =UpdateContext({now: Now()});

  1. Save the file.
  2. Repeat steps 10 & 11 & 12 for any other affected screen/component.
  3. In the command prompt, run the following command, replacing <Username>:
    • .\bin\Debug\PASopa\PASopa.exe -pack C:\Users\<Username>\Downloads\FixedApp.msapp C:\Users\<Username>\Downloads\BrokenApp_src\
  4. The file FixedApp.msapp can be opened in the Studio.

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Join me at 365 and PWR EduCon in Chicago
EduCon Chicago 2022

Frequent Visitor

Looks like this must have worked for OP, but it doesn't solve the issue for us. In production the app works/looks as it should. The exact same production version using the the editor shows each page/component as just a dot or a line. Attempting the ALM solution results in each page/component in the editor as just a dot or a line. Restoring to March is not an option for us as we develop daily. Will be replying back to our support ticket where they gave us the same solution that was given here...

Resolver I
Resolver I

I received the same communication from MS that @Pstork1 posted and haven't tried it yet. I do know that when I was troubleshooting I did try reverting every version (one per day) until I got a version that seemed unaffected. I had to go back to March 11 to get a version that seemed to work. However, much like you I have been working on this one app every day since then and don't really know what changed over the last month with the components that are affected - maybe something maybe nothing.

I think I am going to start using the "GitHub Connector for PowerApps platform" to have some change control. It is just myself working on the apps and I didn't do anything prior to this because I figured the revisions were good enough, but clearly, they aren't in this situation. It would be wonderful to do a diff comparison between the two revisions. 

Resolver I
Resolver I

So following their instruction I did find the last revision of the affected app that was below 3.21032.0  and in my case, it was 3.21031.49 and from March 23, 2021. Using method 1 I was able to open  and load the app and it seemed to not have the problem with the width and height. It is still 2 weeks old though and I dont think I am going to try and recreate any lost progress between then and now. 

Does anyone know what causes the issue? Is it using appwidth.height/width in a component? I would much rather use my latest version of the app (with all current changes) and recreate the components using a different method to proceed. 

Frequent Visitor


PowerApps support has been frustrating to deal with and extremely slow (always 24+ hour response times, sometimes 72 hours). They set our ticket at low impact/low priority despite it being high priority business critical, and we aren't allowed to change it. Attempts to escalate haven't gone anywhere. They did mention yesterday to us that Microsoft released the "official fix" on Friday apparently, but the issue still isn't fixed for us...

In the meantime, I've found a temporary fix, at least for us:
Navigate to
Change your authoring version to 3.21033.47
Go to File > Open, and open your affected app

For us, it opens correctly this way and we can even develop and publish new updates. What I'm afraid of though, is if Microsoft were to never fix this issue and development work continues here on 3.21033.47. That would leave us stranded with no further updates, and once 3.21033.47 is depreciated, we could no longer develop at all...

Helpful resources

Power Apps Africa Challenge 2022

Power Apps Africa Challenge

Your chance to join an engaging competition of Power Platform enthusiasts.

Super User 2 - 2022 Congratulations

Welcome Super Users

The Super User program for 2022 - Season 2 has kicked off!

September Events 2022

Check out all of these events

Attend in person or online, there are incredible conferences and events happening all throughout the month of September.

Government Carousel

New forum: GCC, GCCH, DoD - Federal App Makers (FAM)

In response to the unique and evolving requirements of the United States public sector, Microsoft has created Power Apps US Government.

Users online (2,262)