10 years later, there's still no definitive solution to this issue. How did you handle it?

That's bad news. Am I allowed to use BGAppRefreshTaskRequest or BGProcessingTaskRequest, and a NSMetadataQuery, to watch all the files in the sandbox and manually index in Spotlight the updated ones? This way I can open a file and index each note separately.

What happens if I index the note items from a file by calling CSSearchableIndex.default().indexSearchableItems(allNoteItems) from within the update(_:forFileAt:) of the CSImportExtension, when the system calls it. Will Spotlight register or discard these separate items.

I’ve finally made peace with having to index a notes file as a whole rather than as separate items. However, I’ve run into another issue: I built a CSImportExtension and tested it on iOS. The indexed file appears in Spotlight search results, but when tapped, the app only receives a URL context, not an activity object containing the search query. As a result, I can open the file, but I can’t scroll to the relevant section because I don’t know what the user searched for. The app has its own search feature, but the user has to re-enter the query, which is a poor user experience. If I index the content as a CSSearchableItem, the app receives a CSSearchableItemActionType activity, which includes the query string. However, as you’ve explained, files are meant to be indexed as a whole, not as individual CSSearchableItem objects. I then thought that adding a "Search in App" button would solve this, so I added CoreSpotlightContinuation to the Info.plist. While this does provide the query string in a CSQueryContinuationActionType activity, the button only appears for items indexed as CSSearchableItem. For content indexed via CSImportExtension, the button appears but it opens the Files app instead of my app. The question is: How can I index files using CSImportExtension and still receive the query string in a user activity, rather than just a bare URL context?

I got the same issue, how did you solve it?

The chaotic keyboard (mostly in iOS26). Keyboard frames are off when the app is in a small window, the keyboard layout guide is off as well, sometimes it includes the safe area, sometimes it doesn't. And now I just discovered that showing a popover triggers a keyboardWillShowNotification. WTF??

@Frameworks Engineer I realized that it works correctly on iOS, but not on MacCatalyst. I've filled the feedback FB21911058.