Hi,
I have an assistant that launches using a LaunchAgent and a conditional file path.
The problem is during Setup Assistant sessions (after a macOS update for example) my app launches before the user logs in.
This is due to the Setup Assistant starting a session under Setup User.
Is there a smart/clean way to avoid the agent launching in this situation ?
Visibly launchd configuration files cannot help here. The only solution I see is checking the current user on app launch and abort if it's _mbsetupuser - and this solutions isn't clean at all. I'm not even sure it is possible under sandboxing.
Any Help ?
Regards,
Jerome