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?

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.

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.

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

How can I send you the test project? I cannot attach the zip here. In viewDidLoad I set the button, and it looks ok. Then, when the user initiates some action, I replace it with another button, and now it gets a double border. override func viewDidLoad() { super.viewDidLoad() self.navigationItem.leftBarButtonItem = Button1() } @objc func fullscreenAction() { // upon this assignment the leftBarButtonItem shows double border self.navigationItem.leftBarButtonItem = Button2() }

Why does Apple keep removing settings like these? Is there any reason for this? In my case, I need to set the date as well as the time, because I create screenshots on different days, and they end up with different dates, which is not consistent. If I change the date on my Mac and create screenshots on different days, when I later retrieve them from Finder, they get mixed in with other files I created on those days. It's really annoying.

2025, same situation. I've completely stopped filing FB reports. They never respond, yet they keep asking us to file them in various threads on this forum.

Still broken in the latest beta 14.4.

Still occurring in Xcode 16.4 beta (16F1t).

This bug is getting ridiculous, now the debugger complains that ""fromValue" is not a member of "(QuartzCore.CABasicAnimation) picAnim"".

Xcode 16.3 beta (16E5104o) exhibits the same issue.

Also look under the "Other Installed Platforms" section in Xcode settings. It is those platforms that are taking up space in /Library/Developer/CoreSimulator. You can remove, from Xcode, the one that you don't need.

There are 3 projects in a workspace. The main project and two separate projects for two static libraries. Both static libs depend on a framework, a regular framework not a XCFramework. Everything is built from scratch, I own all the source code. The code for the framework is in a swift module. I set "DWARF with dSYM" on all the three projects, it was DWARF only for the libs, but no luck. I can debug the source code from the main project, it works just fine. However, the two static libraries contain the majority of the functionality and I can't debug it. I was adding logs here and there but it takes a lot of time.

Sorry, this Xcode16 just sucks. I've lost another half a days fiddling around with no luck, I just don't know what to do, and where. The project is big and in order to recreate the functionality, and the lldb bug, I have to build a whole new project, which will end up resembling the original one, minus some functionalities, so I dropped this route. The issue appears in one of the projects's internal static library. Now, I pause the execution at some breakpoint, run the "po" command and promptly get the "Couldn't realize Swift AST type of self". Then I run "swift-healthcheck", check the health log file, find the error below and conclude that the issue is in the static lib "XXX". SwiftASTContextForExpressions(module: "XXX", cu: "AllParts.swift")::LoadOneModule() -- Missing Swift module or Clang module found for "XXX", "imported" via SwiftDWARFImporterDelegate. Hint: Register Swift modules with the linker using -add_ast_path. Then I added "-add_ast_path" on the "Other Linker Flags" of the final executable, and now I get an error in Xcode saying "Unknown argument -add_ast_path". The static lib build settings have no "Other Linker Flags", and I don't know where else I should add this flag?! I mention that the I get a message in the console warning about empty dSYM file, but the executable is built with "DWARF with dSYM File", I triple checked it. warning: (arm64) /Users/SomeUser/Library/Developer/Xcode/DerivedData/SW-ajoovsaqjdvysgbbrebnfmoxycwm/Build/Products/Debug-maccatalyst/SW.app/Contents/MacOS/SW empty dSYM file detected, dSYM was created with an executable with no debug info. I'm not sure what you are asking here "Does that file reference UIKit types but is missing an import declaration?". Yes, it uses UIKit types but there is an "import UIKit" directive at the begining of the file where the breakpoint is.

The same, even with the latest Xcode, 16.2.