Answered

Published app behaves differently than edited app

(0) Share

Report

Posted on by RaymondWood

My Canvas Components are displaying differently in Published vs edit mode. See images. In the published version the home icon is scaled up and the text is on two rows. Note that the icon is programmatically, statically sized meaning that it is defined as icon.Height=30 and icon.Width=30. This component is from a component library but on other screens, local Canvas components are showing the same behavior.

Published App

App in Dev Environment

This issue has held up app development for a week now. Just when I thought I had it corrected, it reared its ugly head again.

In case it helps, I did recently do a revert to the previous commit in Azure Repo.

I don't know if this is a settings issue or a repo issue but it is definitely not a source issue(at least not source that is accessible through the IDE). I don't know what happens at the system layer when I commit a change but I feel like that is where this gremlin gets introduced.

I have the same question (0)

All responses (5)

Answers (1)

RaymondWood 61 on at

Like (0)

Report

Re: Published app behaves differently than edited app

Was this reply helpful? Yes No
MarkRahn 1,147 Super User 2025 Season 2 on at

Like (0)

Report

Re: Published app behaves differently than edited app

Hi @RaymondWood ,

Is the Header the only Component on the form? Was this Component imported? Is this component used in any other Power Apps?

In Settings, what is "Display" - "Scale to fit" and "Lock aspect ratio" set to?

For the Header Text Label, what is the Width and Wrap properties set to? Are these exposed in the Component?

If this response has helped you, please consider giving it a thumbs up. Thanks.
-Mark

Was this reply helpful? Yes No
RaymondWood 61 on at

Like (0)

Report
Re: Published app behaves differently than edited app

Thanks @MarkBandR but all of the considerations you mention have been looked into. The fact that playing the published copy yields a different result than the same version in the IDE player, using the same device, was very alarming and feels like a compiler issue. How can I rule this theory out?

I have narrowed it down a little. Let me be more specific.
I have this problem across a few canvas components in the same app.
All canvas components are local
They only render incorrectly in Live (publish/play),
Live version is the latest version,
I am working on the same device
App design setting is responsive
Same component only renders incorrectly on some of the app screens
On Screen 2 the same component renders differently than on the other screens
they come from the same local component (I even copy pasted from a good screen to the other)
After inspecting the rendered HTML, the affected controls in the components are containers
The containers are set to specific size example 48px x 48px, auto height, auto width are off
As an example a specific container in a component on screen 2 renders as 500px x 200px, in the yaml it is set to 48px x 48px
The same container in the same component on Screen 3 renders as expected 48px x 48px
When played in the IDE, everything renders fine.

Was this reply helpful? Yes No
RaymondWood 61 on at

Like (0)

Report

Re: Published app behaves differently than edited app

I have other offending containers in other components doing the same thing.
When I looked into the offending container in the offending instance of the component (Screen 2 vs screen 3), I found the height and width had rendered to 500 x 200. The set height and width in the container is 48 x 48. Can this be due to compiler error?

The containers are designated as groupContainers which are set to default to 500x200 in the groupContainer.xml file. So why are specific containers defaulting?

Was this reply helpful? Yes No
Verified answer

RaymondWood 61 on at

Like (0)

Report

Re: Published app behaves differently than edited app

It looks like the first displayed instance of the offending components are the ones that act up. Subsequent instances behave.

After adding an instance of each of the offending components to the start screen, the components on the other screens behave normally.

Was this reply helpful? Yes No