Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OK I need someone to explain this to me. I have been checking indexing progress for a week now. Tonight I went to console and typed in the command and pick my phone one the side bar I had not yet plugged in the USB C cable and it still started to show the percentage and kept doing so. how is my Mac getting this info if my iPhone is not connected to it via a USB cable?
 
OK I need someone to explain this to me. I have been checking indexing progress for a week now. Tonight I went to console and typed in the command and pick my phone one the side bar I had not yet plugged in the USB C cable and it still started to show the percentage and kept doing so. how is my Mac getting this info if my iPhone is not connected to it via a USB cable?
Over bluetooth.
 
Was at 90% when checking last Tuesday...

Still at 90% now, coming up on 2 weeks after the install, so I wouldn't be surprised if it goes over the initially estimate of 1-2 weeks. 😉

15 pro.
 
I did some digging around in the console, and there's definitely an indexing bug on some devices, including my 14 Pro.

At first I thought maybe it's taking a really long time to index my photos, music, or mail because those are the apps that have the most data - thousands of photos, songs and emails.

So I went into Settings > Search and disabled spotlight indexing for those apps, and then rebooted the phone. But the indexing message persisted.

Then I figured, why not search for errors related to Spotlight in the Console app. And I found this:

1782120668736.png


and this:
1782120746646.png


Now, pardon my lack of expertise in the internals of the iOS operating system, so I consulted Gemini, and this is what it said:

1. The Real Culprit:​

Look at Screenshot 2026-06-21 at 1.56.26.png:

/usr/libexec/dasd ... coalitionID not found after refresh, for identifier=spotlightknowledged
dasd is the central brain iOS uses to manage background battery life and smart resource scheduling. It evaluates device temperature, battery state, and CPU load to decide which background tasks are allowed to run.

A "coalition" in Darwin/iOS kernel terms is a resource-tracking group (CPU, memory, I/O allocations) tied to specific tasks. The error coalitionID not found after refresh means that dasd went to manage or throttle the resource budget for spotlightknowledged, but discovered the process group had already vanished, crashed, or desynchronized from the kernel's active task tracking list.

2. The Chain Reaction​

Look at Screenshot 2026-06-21 at 1.56.47.png:

### Connection(0x7db6cbe940) invalid pid: 379 (Preferences)
Because dasd loses track of the coalition tracking, the system kernel steps in and abruptly kills the target processes to protect the phone's memory stability.

  1. spotlightknowledged.updater requests data from the Preferences engine.
  2. The beta codebase hits an unhandled exception or attempts an unauthorized memory access.
  3. dasd detects the erratic behavior, fails to refresh the process coalition budget, and the kernel immediately halts Preferences (PID 379).
  4. spotlightknowledged logs the invalid connection, and the whole cycle restarts.

Essentially, those of us stuck at the same indexing percentage should just wait for beta 2 and hope it gets fixed.
 
  • Like
Reactions: TheCart and papbot
I did some digging around in the console, and there's definitely an indexing bug on some devices, including my 14 Pro.

At first I thought maybe it's taking a really long time to index my photos, music, or mail because those are the apps that have the most data - thousands of photos, songs and emails.

So I went into Settings > Search and disabled spotlight indexing for those apps, and then rebooted the phone. But the indexing message persisted.

Then I figured, why not search for errors related to Spotlight in the Console app. And I found this:

View attachment 2640036

and this:
View attachment 2640037

Now, pardon my lack of expertise in the internals of the iOS operating system, so I consulted Gemini, and this is what it said:



Essentially, those of us stuck at the same indexing percentage should just wait for beta 2 and hope it gets fixed.
My understanding was that this has always been a bug needing correction in beta 2, ideally today. Although I haven’t checked on my Mac, after two weeks, indexing persists—while others here, with much larger data and photo libraries than mine, no longer see the message—so this clearly seems like a bug.
 
I had indexing stuck at 87% for 5 straight days and sometime last night it went away.

NOW WHAT
🙂

All that anxiety and now I dont know whats next ...
 
I wonder if Apple did disable the progress bar but it's still happening behind the scenes. I now see the below in console under Beta 2, and my indexing didn't finish on Beta 1.

PipelineCompleteness: not showing, showOverallPercentage: false
 
  • Like
Reactions: Mehaly
After updating the indexing, it's still there. I'll get over it. I think we were used to not seeing that the iPhone always performed this operation in previous iOS versions, but it just wasn't visible.
 
After updating the indexing, it's still there. I'll get over it. I think we were used to not seeing that the iPhone always performed this operation in previous iOS versions, but it just wasn't visible.
No indexing here. Two weeks of indexing resolved by the second beta. Always considered this a bug. I’m certain indexing occurred but for those of us with very low amounts of overall data it should have completed in a couple days at most, just as it always did on my mac, and even on my mac it never took more than that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.