sindresorhus/LaunchAtLogin-Legacy

Parent application is being launched instead of the launcher

thermogl opened this issue · 1 comments

This is a weird one I can't understand. We're seeing an issue whereby toggling LaunchAtLogin.isEnabled causes a whole new instance of the parent application to launch instead of launching the LaunchAtLogin application and toggling off causes that instance to be terminated.

When checking in Console.app I can see the embedded application is being registered, but for some reason the system is launching the parent:

registered file:///private/var/folders/4x/7vnxj2dx7zj6jrjgfvyjwjq40000gp/T/AppTranslocation/28874F2B-823A-4B85-880E-0C2BEC28A867/d/MyApp.app/Contents/Library/LoginItems/LoginLauncher.app/ (status 0, old id 0x4e9c) as unit 0x4ea0 on behalf of pid 3834

Anyone seen this before?

Seems to only happen when the app is launched into a quarantined environment (eg open directly from Downloads). When dragging to Applications before launching the issue is not reproducible.

Can anyone else confirm?