Messed up UTIs in NSDocument-based application
Messed up UTIs in NSDocument-based application
- Subject: Messed up UTIs in NSDocument-based application
- From: Donald Ness <email@hidden>
- Date: Tue, 10 Jan 2012 21:26:12 -0600
So I recently shipped a document based application to the App Store with an unfortunate oversight: the UTI for the main document type was left blank, and wasn't exported. I had a name for it, but the identifier was straight up empty.
Everything still worked great, but then I went to add another file type to the mix in the next version. The new file type is simply xml (conforms to public.xml). I set that up and dropped it into the document. This is when I caught the oversight on the first document type's UTI.
I entered an appropriate identifier for my main document type, and added it to my exported UTI list. Now when I try to open my document types from my application, they are grayed out in the open dialog.
To recap, I released a document-based application with this:
Document Types:
1.) Name: "My Document", Extension: "myext", Identifier: ""
Exported UTIs: (none)
Imported UTIs: (none)
And now I have this:
Document Types:
1.) Name: "My Document", Extension: "myext", Identifier: "com.mycompany.myext"
2.) Name: "My XML Document", Extension: "xml", Identifier: "public.xml"
Exported UTIs: "com.mycompany.myext"
Imported UTIs: "public.xml"
However, I my main document type is grayed out in the open dialog now. I'm at a loss as to how file types are associated with applications, and how to fix this issue.
I really want to clean this up, so what's the best way to do so?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden