App-Logo missing after Update to 5.3.2

Tried the following:

I created a new app with no content or code at all.

When I use “New-App -Logo “logo.png” -Content {}”, the logo is shown. Changing “-Content” to “-Pages $AppPages” (where $AppPages is an array with just one empty page), the logo is still there.

Then I paste some code in the page (just a New-UDColumn with one New-UDCard and some text), and the logo is gone.

Even if I revert this code to “Hello World”, it will not show again. I have to delete the complete page und create a new one.

I don’t get it…

The GitHub-Case states this issue as solved with version 5.4.0 (Missing App Logo After PSU 5.3.2 Update When Using -Pages Parameter in New-UDApp · Issue #4434 · ironmansoftware/powershell-universal · GitHub), but after updating to 5.4.1 yesterday its unfortunately still not working.

I have this same problem using 5.4.3 I was about to post a new topic. Would be great to know when this will be fixed.

This seems to be case regardless of whether or not an icon has been specified for the page.
Also, if you do specify an icon in the settings for the page it does not allow you to remove the icon when editing the App Page settings. That may be a different bug altogether.

Thank you - good to see that I’m not the only one.

I’ve added a comment to the github issue, unfortunately I didn’t get a response on my support ticket right now.

Same issue here, still not working as of 5.4.4. Adam marked the bug as closed.. perhaps it will be in next release?

It’s frustrating.

I’ve installed 5.5.1 as a test and there it works - I can set and revert the settings and still see the logo.

Today I’ve updated my production server to 5.5.1 - and it does not work…

The bug is closed the second time without a comment, the support case is open but still not commented.

Can you please provide the support ticket number?

Ticket number is #10447 (the content is nearly the same as in the github bug).

Today I tried to reproduce the issue for a network trace. I deleted the app page and created a new one and the error is gone. I also tried this in my production environment (delete app page, create new one, restore code) and it works, too.

Perhaps it was a bug in one of the older versions - with 5.5.1 now it works if you recreate the app pages.