Stop working when plug in or out my setup

[incline02]

Required information

In order to help us sort your issue, we ask that you provide the following information:

• Mac model: M1 Pro
• macOS version: Sonoma 14.2.1
• Monitor setup: 2x Ultrafine 27 inch (laptop in clamshell)

Description of issue / Feature request

Issues: When I unplug my laptop from the dock, screensaver and desktop server revert back to MacOS's saver.
Issues: Same when I plug it back in

I have to manually click the icon in the menu bar, click the icon with the dock inside the screen to manually start Aerial's video and it's back to normal.

[glouel]

Hi @incline02

Let me try to split the issues here for a second :

First the screensaver : Can you check your screensaver panel and see if "show on all spaces/screens" is on too on your setup ? One new thing in Sonoma is that you can have different screensavers on all your screens. It's possible that you installed aerial in Clamshell mode, and because of that your screen is "unknown" to the system. So out of clamshell, check if Aerial is still selected here or not and let me know what you see.

Wallpaper, are you using Companion's desktop mode ? If I understand right, you have to press again that thing :

Right ?

I'm not totally surprised if that's the case, because Companion can't know that you were in clamshell mode and is just confused I guess. This is something I can likely fix in an upcoming version, but I may need your help testing as I don't have such a setup available to me.

[incline02]

Hello, thanks for the reply!

Yeah show on all spaces is toggled on!

So when I unplugged it and open it, the first thing I see is MacOS screensaver (lock screen). I unlock and the desktop shows Aerial. I start the screensaver again and Aerial is up again.
When I plug the laptop back in, lock screen is macOS screensaver, I unlock, it says the same. I start the screen saver again and it's Aerial. I unlock and it's still macOS

and yes, to solve the latter, I got to click on that icon you pointed at!

Yeah of course I'm available for assist!

[glouel]

Ok so, as far as I understand :

• Screen saver is always Aerial
• Lock screen is not Aerial
• Companion doesn't understand your screen switching

1 is good then.

2 is normal, right now the lock screen will always be the default Apple thing, you can't change that. Companion 2 will have some intermediary mitigation by changing your default macOS wallpaper to have that on the lock screen instead.

3 is the bug in Companion, I'll have a look and ping you when I have a beta for you to test !

[incline02]

Superb ! Looking forward! Thank you for bringing this UX to the Mac in a much better fashion than apple ! Standing by for the beta !

…

On 23 Feb 2024, at 23:34, Guillaume Louel ***@***.***> wrote: Ok so, as far as I understand : Screen saver is always Aerial Lock screen is not Aerial Companion doesn't understand your screen switching 1 is good then. 2 is normal, right now the lock screen will always be the default Apple thing, you can't change that. Companion 2 will have some intermediary mitigation by changing your default macOS wallpaper to have that on the lock screen instead. 3 is the bug in Companion, I'll have a look and ping you when I have a beta for you to test ! — Reply to this email directly, view it on GitHub <#1363 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A24JNOBQLF22IUSKM3KCRE3YVEKQRAVCNFSM6AAAAABDXHZ7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGA4DSNJVHA>. You are receiving this because you were mentioned.

[lameyer]

I'm running into this as well. Aerial Companion thinks it is running correctly after I re-plug in to my set up, but the desktop is just the Mac default. If I pause and restart in the Aerial dropdown, it starts working again. But if I click the stop icon instead of pause, Aerial crashes completely.

I thought I could work around this by creating a Shortcut to close/reopen Aerial Companion. It either fails to open the app or succeeds but throws this error:

Adding a Wait of 1s before re-opening app does seem to have solved the fail case, so I think this shortcut will work for me