It's working again now.
I still wished this was mentioned on https://developer.apple.com/system-status/ whenever it goes down.
Schubert
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
How? Java isn't installed on macOS.
It's not working for many developers.
Again this is no longer working for me. Am I alone with this problem or can anyone else confirm this?
I updated to the release candidates of Monterey 12.1 and Xcode 13.2 and the problem persists. One would think this should be a top priority issue.
I'm having the exact same problem. Of course the Apple Help Programming Guide was last updated in 2013. It feels as if Apple is actively discouraging help books.
It's working again (without me having done anything). So I guess this was a fluke in the AppStore.
[QUOTE]Indeed. That should give you some idea as to the general disposition of this technology )-: Most of the focus these days is on Core Spotlight.[/QUOTE]Core Spotlight isn't a direct replacement for Spotlight Importers, is it?Core Spotlight only works for database-like applications (the exception on macOS). There doesn't seem to be a more modern replacement for custom document files. So everybody who has a custom file format still needs to write a Spotlight Importer.Thanks to your hint and the Internet I have gotten it to work like this:The Spotlight Importer template is included in Xcode 8, which is still downloadable. The template is included atXcode.app/Contents/Developer/Library/Xcode/Templates/Project\ Templates/Mac/Other/Spotlight\ Importer.xctemplateThe "Spotlight Importer.xctemplate" can be copied to~/Library/Developer/Xcode/Templates/Spotlight\ Importer.xctemplateand Xcode 11 will pick it up and happily create Spotlight Importer targets again.The sample target is Core Data centric and uses some deprecated API - maybe that's why it was removed. After removing the unnecessary Core Data parts it works fine for custom file formats and without deprecation warnings.