We have an internal user who consistently runs into the application not starting after update completes. They have to start it manually, and it appears to be running the updated version after that.
ShipIt logs are kind of non-indicative:
2023-02-03 08:17:19.904 ShipIt[37774:1971920] Detected this as an install request
2023-02-03 08:17:22.916 ShipIt[37774:1971922] Beginning installation
2023-02-03 08:17:25.257 ShipIt[37774:1971922] Moving bundle from file:///Applications/Signal%20Alpha.app/ to file:///var/folders/1x/4x6d28yn5b17k60r4zmyvpj00000gn/T/org.whispersystems.signal-desktop-alpha.ShipIt.1kAFz2dv/Signal%20Alpha.app
2023-02-03 08:17:25.258 ShipIt[37774:1971922] Moving bundles via 'Contents' folder rename
2023-02-03 08:17:25.258 ShipIt[37774:1971922] Moved bundle contents from file:///Applications/Signal%20Alpha.app/Contents/ to file:///var/folders/1x/4x6d28yn5b17k60r4zmyvpj00000gn/T/org.whispersystems.signal-desktop-alpha.ShipIt.1kAFz2dv/Signal%20Alpha.app/Contents
2023-02-03 08:17:25.258 ShipIt[37774:1971922] Moving bundle from file:///var/folders/1x/4x6d28yn5b17k60r4zmyvpj00000gn/T/org.whispersystems.signal-desktop-alpha.ShipIt.7z1bWQEj/Signal%20Alpha.app to file:///Applications/Signal%20Alpha.app/
2023-02-03 08:17:25.258 ShipIt[37774:1971922] Moving bundles via 'Contents' folder rename
2023-02-03 08:17:25.258 ShipIt[37774:1971922] Moved bundle contents from file:///var/folders/1x/4x6d28yn5b17k60r4zmyvpj00000gn/T/org.whispersystems.signal-desktop-alpha.ShipIt.7z1bWQEj/Signal%20Alpha.app/Contents/ to file:///Applications/Signal%20Alpha.app/Contents
2023-02-03 08:17:25.302 ShipIt[37774:1972050] On main thread and launching: file:///Applications/Signal%20Alpha.app/
2023-02-03 08:17:25.302 ShipIt[37774:1972050] Bundle URL is valid
2023-02-03 08:17:25.302 ShipIt[37774:1972050] Attempting to launch app on 11.0 or higher
2023-02-03 08:17:25.302 ShipIt[37774:1972050] Launching new ShipIt at /Applications/Signal Alpha.app/Contents/Frameworks/Squirrel.framework/Resources/ShipIt with instructions to launch file:///Applications/Signal%20Alpha.app/
2023-02-03 08:17:25.303 ShipIt[37774:1971922] Installation completed successfully
2023-02-03 08:17:25.305 ShipIt[37774:1972050] New ShipIt pid: 37787
2023-02-03 08:17:25.409 ShipIt[37787:1972151] Detected this as a launch request
2023-02-03 08:17:25.490 ShipIt[37787:1972151] Successfully launched application at file:///Applications/Signal%20Alpha.app/
2023-02-03 08:17:25.490 ShipIt[37787:1972151] ShipIt quitting
2023-02-03 08:17:25.490 ShipIt[37774:1972050] ShipIt status 0
2023-02-03 08:17:25.490 ShipIt[37774:1972050] New ShipIt exited
2023-02-03 08:17:25.491 ShipIt[37774:1972050] ShipIt quitting
and in fact are identical to logs from users who don't run into any issues.
Is there any additional information that we could collect from the user?
We have an internal user who consistently runs into the application not starting after update completes. They have to start it manually, and it appears to be running the updated version after that.
ShipIt logs are kind of non-indicative:
and in fact are identical to logs from users who don't run into any issues.
Is there any additional information that we could collect from the user?
cc @MarshallOfSound