[osy]

The screenshot is (obviously) from a jailbroken phone. Currently nobody with a stock phone can reproduce it (through Console on a Mac with Developer Mode enabled) although you are free to try it and test for yourself. This is just another side effect of how jailbreaks make your device more unstable.

[whywhywhywhy]

Isn't something deeply broken if that would cause issues with something as superfluous as ad tracking?

[vore]

I feel like all bets are off if you're modifying your phone away from what the manufacturer explicitly supports. Not saying you shouldn't, but this says nothing about the brokenness of the stock software.

[EPWN3D]

No.

[dylan604]

Sorry, for those of us that are not mobile devs, how are the white text on black background obviously signaling that it is jailbroken?

[shinratdr]

You wouldn’t be able to see that debug information on the phone itself if it wasn’t jailbroken, as the GP mentioned you would need to use console on a Mac. The second screenshot is from a phone, ergo, jailbreak.

Also other commenters have mentioned he’s on 15.4.1. That’s two major iOS versions old. It’s possible they’re just on an iPhone 6S/SE/7 which was capped at that version, but a jailbreak is likely.

[saagarjha]

The console message is from an app for jailbroken devices: https://github.com/NSAntoine/Antoine

[slantedview]

Does jailbreaking somehow cause Apple ad tracking to run as a daemon? Maybe you can explain how these things are possibly related.

[TheCleric]

My guess? The ad tracking is a daemon regardless, but when you disable it regularly it disables the daemon. However when jailbroken, there may be code within the jailbreak or an assumption within the OS code that has two processes fighting over starting it and stopping it.

For example the jailbroken code might have something that tries to keep all daemons running and the OS sees the ad one running and tries to kill it.