Steps to Self-Mitigate

elkolorado · ‎04-06-2021

Hi,
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 https://www.youtube.com/watch?v=-HLLF2ZRaXc.

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

Pstork1 · ‎04-08-2021

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.

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

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.

Navigate to https://create.powerapps.com/v3.21032.45.181423928/studio/#noRegionRedirect

If the Studio opens in an incorrect environment:

Open a new incognito/guest window
Go to https://make.powerapps.com
Select the desired environment
Navigate to https://create.powerapps.com/v3.21032.45.181423928/studio/#noRegionRedirect

Go to Open > Power Apps (Browse Power Apps) > Select the affected app
Select the affected screen in the tree view (it should appear normally).
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).

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.

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

Download and install the .NET Core SDK 3.1 .
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

Run the command .\build.cmd. The command prompt will show "Build succeeded" when complete.

Keep this command prompt open for later.

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 (make.powerapps.com ), 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.
Extract the downloaded .zip file
Find the .msapp file in the extracted package. You should be able to type .msapp in the search bar.

Copy the file to your Downloads folder and rename it to something a little more convenient, eg: BrokenApp.msapp
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.

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).

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()});

Save the file.
Repeat steps 10 & 11 & 12 for any other affected screen/component.
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\

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.

View solution in original post

Pstork1 · ‎04-06-2021

I've seen several people report this, but it is far from everyone. I would suggest opening a support ticket to get it resolved for you.

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

bcampbell13 · ‎04-06-2021

I can confirm I'm having a similar issue. It may be be everyone, but I would guess many have not tried to editor there app today. Something was definitely done created a problem for some "unknown" set of users. Very frustrating.

Pstork1 · ‎04-06-2021

I agree that its frustrating. But I've seen posts from a few users for about a week now. The point is that its not everyone so there is nothing we can really do for you here in the forums. Its something MS has to look at from the inside. To do that they need specific cases. That's why a support ticket is important.

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

BrianCCampbell · ‎04-06-2021

I too have this happen to one of my PowerApps that I edit every day (getting ready to release but not used by others yet). This started for me either 4/3 or 4/4 or earlier and I just want on a screen that was affected. All of my screens use components and not all are affected - but almost half are. I also noticed I was seeing "Invalid operation divisible by zero" errors show up and they were cascading and incrementing higher when the app was open. I found the other thread with that error and changed my logic to include an if statement if the count of something in the denominator could possibly be zero. Even after these updates, it had no effect on the problem of the width.

I did some troubleshooting, but it all comes down to the fact that the component in a screen has a width and height of Zero. Even after changing the width or height to another value - when leaving the field it would revert to Zero. When looking at the components themselves in the components section, they have the proper height and width specified. I created a new screen and tried to insert a component and it. came in with Zero height and Zero width.

I created a new app, imported the components from the problem app and it only imported 6 of the 9 components. (no error - just left 3 of them out). I then exported the components from the problem app and imported to the test app and all came in. When adding a component to the screen it adds but lists "No Value" for the width and height despite the formula for both being app.designheight and app.designwidth. Changing the value for height and width to the real numerical value makes the component appear as expected.

The problem app and the test app are the only apps I have in this environment and the environment has the settings enabled to run the GeoSpatial Maps.

I have another powerapp in production in a separate (default) environment that also uses components but I have not edited so it doesn't appear to have any issues.

It's also ironic that @bcampbell13 is having issues as I think we possibly share the same name.

I will submit a support ticket to see if I get any traction.

Pstork1 · ‎04-06-2021

MS is aware of the issue and support can suggest some workarounds for the immediate future. A fix has been identified and should roll out in the next week or two.

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

bcampbell13 · ‎04-06-2021

@Pstork1 ,

One to two weeks, that is really very painful. Microsoft has a reputation of their users being the testers, and I have to say with PowerApps, it really feels like this is the case.

This has happened several times. How do they expect companies to embrace this technology and rely on when they create outages like this. My dev team lost the entire day. Waiting two weeks is painful. Every time you touch a component, it resets them in the app, every occurrence of them. The component frame work is great in concept, but pretty less then great in reality.

Really disappointing from a company such as Microsoft.

Pstork1 · ‎04-06-2021

Did you open a support ticket? I can forward the number to someone I know on the team to get it escalated.

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

BrianCCampbell · ‎04-06-2021

Hi @Pstork1 @yes I did. The ticket number is

2104060040007229. Thanks for your help in this.

elkolorado · ‎04-07-2021

Hi @Pstork1 thank you for reply.
As Brian mentioned, if you try to set the width of screen to a proper function it does that, but then the components width is still 0, and while trying to set width and X-position on Properties tab from 0 to what it supposed to be (that information is saved inside Advanced Tab still) it goes back to 0, but after you choose different value it sets properly. But at the point where I have 4 screens not working with 20+ components setting all of this manually is no-go in terms of the time and deadlines.

I also raised a ticket to Microsoft about this.
Ticket number:
2104070050000542

Thank you for your patience