I've also noticed that instead of mentioning the API level, it becomes a useless "(1)" and "(2)" . Please restore this too.

I reviewed the behavior of the old dialog for a non Play and a Play device

Pixel 6 (non Play)

Enable device frame = false

skin.dynamic=yes
skin.name=1080x2400
skin.path=_no_skin
skin.path.backup=/home/juancnuno/Android/Sdk/skins/pixel_6

If you set Enable device frame to true and select No Skin in the drop down, the checkbox resets itself to false

skin.dynamic=yes
skin.name=1080x2400
skin.path=_no_skin
skin.path.backup=_no_skin

Pixel 9 Pro (Play)

Enable device frame = false

skin.dynamic=yes
skin.name=1280x2856
skin.path=_no_skin
skin.path.backup=/home/juancnuno/Android/Sdk/skins/pixel_9_pro

If you set Enable device frame to true the drop down is set to pixel_9_pro and is disabled. You can't change the value.

skin.dynamic=yes
skin.name=pixel_9_pro
skin.path=/home/juancnuno/Android/Sdk/skins/pixel_9_pro

@3 Whatever the reason, please bring it back. There is no reason that having the Play Store on the emulator will force me to have a useless frame of the device around the window.

I don't need this frame. Never needed it. On the new UI of the canary IDE, I can't disable it. Only on the previous version of the IDE, on stable.

There is no reason for the checkbox to ever be un-checkable. It's only a skin...

Why is it marked as fixed? On which version of the IDE?

We typically mark bugs fixed when the changes are merged. It helps with release tracking, etc.

The changes should go out in Meerkat Canary 4

@6 Please change it so that we see on which version from now on, each time something is marked as "fixed"

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Meerkat | 2024.3.1 Canary 4
• Android Gradle Plugin 8.9.0-alpha04

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

@8 For some reason it still says the same message. What does it mean? In which cases would it prevent me from doing something, what, and why?

Why not have some indication in the UI for them, and maybe some explanation or a link?

For reasons I myself am not entirely clear on, the Expanded storage type, number of CPU cores, Graphics acceleration, RAM, and VM heap size UI elements are not enabled when you use a Play image. I carried this behavior over from the old dialog. If you would like us to continue to explore the UI treatment, please file another bug.