[BUG]: Panel background color not rendering properly with the default parameters

[tiagomiotto]

Describe the bug
I've tried including the Panel component on an existing app. However, the Theming functionality is broken, as the background of the Panel is shown as black instead of white. This is without changing any values on the Panel component or setting the AppTheme variable as explained in the Docs.

Setting the AppTheme seems to break everything in terms of theming, as even the buttons become invisible, which I suspect is because if I try to set the AppTheme variable the component is not able to read it and causes an error.

To Reproduce
Steps to reproduce the behavior:

1. Import the CreatorKit solution
2. Open an existing app in the environment
3. Add the Panel component to the app

Expected behavior
I expected the Pannel background to be white, as it is the default value.

Screenshots

Additional context

AB#964

[tiagomiotto]

Found the Bug.

Apparently, if we are importing the components into an already existing app, the Color.Transparent call is spawning an error for some reason, saying that it doesn't exist. This does not happen with the Canvas Template.

I was able to create a workaround:

1. Open the Component Library in Edit mode
2. Change the Description of the Library
3. Save and Publish
4. Open my App again, and import the changes from the Component Library

This creates an unmanaged layer on the Component Library, with the only change being the Description, and it fixes the issue. It makes me suspect the issue is coming from some lacking metadata on the original layer.

[IsabelleRioux]

A similar issue was reported and resolved during the april release.
#295

[packman83]

Found the Bug.

Apparently, if we are importing the components into an already existing app, the Color.Transparent call is spawning an error for some reason, saying that it doesn't exist. This does not happen with the Canvas Template.

I was able to create a workaround:

1. Open the Component Library in Edit mode
2. Change the Description of the Library
3. Save and Publish
4. Open my App again, and import the changes from the Component Library

This creates an unmanaged layer on the Component Library, with the only change being the Description, and it fixes the issue. It makes me suspect the issue is coming from some lacking metadata on the original layer.

I had to do this when installing today's release for the issue to be resolved in existing and new apps. Is this a bug within the Creator Kit solution or our own apps?