Skip to main content

Jamf Pro macOS Onboarding fails to start with error: LaunchDarkly failed to init

Updated over 3 weeks ago

Issue Description

During computer setup macOS Self Service will launch successfully but macOS Onboarding will not properly kick off.

In the Self Service logs (debug not needed), we will see a line similar to the following:

[2024-10-16 09:56:15] LaunchDarkly failed to init

This can happen due to blocking LaunchDarkly domains. Self Service defaults macOS Onboarding to 'off' so, when a machine cannot reach LaunchDarkly's servers, it will not know to enable the feature for that particular computer.

LaunchDarkly is a development framework that Jamf uses for many of it's client-side applications. It allows developers to toggle features on/off easily in Self Service (or other client side applications). It does not collect any data, it only grabs the current settings from LaunchDarkly and applies them.

Troubleshooting Steps

Presently we are working on getting Technical Communications to add LaunchDarkly domains to our networking documentation. In the meantime, we can leverage LaunchDarkly's own documentation to see which domains our clients need to access in order for macOS Onboarding to properly function.

Did this answer your question?