Re: Another app's UTI can break your app
Re: Another app's UTI can break your app
- Subject: Re: Another app's UTI can break your app
- From: Noah Desch <email@hidden>
- Date: Wed, 11 Jun 2014 18:12:25 -0400
On Jun 10, 2014, at 3:21 PM, Seth Willits <email@hidden> wrote:
> My app and Coda both open plain text .sql files. Coda exports a UTI for the .sql extension. So does my app.
If .sql files are a public format that was defined by neither your app nor Coda, you should both be *importing* UTIs for it, instead of *exporting* them. I wonder if this problem would occur if both of your apps only declared the .sql type as imported?
Exporting a type means you have defined that type and you control it. Importing a type simply means you would like to use it. Does it fix your app if you change your declaration to an import?
Regardless, an incorrect export declaration shouldn’t break other apps that happen to use that UTI. It’s interesting that the documentation says what happens when you have multiple importers and one exporter (the typical case) but not what happens when there are multiple exporters (the error case).
My (possibly flawed) understanding is based on:
https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/understanding_utis/understand_utis_declare/understand_utis_declare.html
-Noah
_______________________________________________
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