Just a shot in the dark, but maybe this is an issue: 

Comparing your declaration to the sample from 
<https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/understanding_utis/understand_utis_declare/understand_utis_declare.html>
 reveals that the sample declares com.apple.ostype 
directly as an string: 

                ..
                <key>UTTypeTagSpecification</key>
                <dict>
                    <key>com.apple.ostype</key>
                    <string>JPEG</string>
                    <key>public.filename-extension</key>
                ..

whereas your sample uses an array with one string. 

Cheers, 

Felix


On 16.10.2014, at 13:07, Graham Cox <graham....@bigpond.com> wrote:

> It is a dyn.<blahblah> type, which indicates that the UTI for the given file 
> extension is unknown. So this is the puzzle - why, having exported a UTI for 
> that very extension (.cxtf), is it still returning unknown, even after 
> rebuilding the database, safe rebooting, etc. My export declaration must be 
> incorrect, but AFAICS it looks fine:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" 
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
> <plist version="1.0">
> <array>
>       <dict>
>               <key>UTTypeConformsTo</key>
>               <array>
>                       <string>public.content</string>
>               </array>
>               <key>UTTypeDescription</key>
>               <string>Crucible File</string>
>               <key>UTTypeIconFile</key>
>               <string>crucibledoc</string>
>               <key>UTTypeIdentifier</key>
>               <string>net.apptree.crucible.newcrossfile</string>
>               <key>UTTypeTagSpecification</key>
>               <dict>
>                       <key>com.apple.ostype</key>
>                       <array>
>                               <string>CXTF</string>
>                       </array>
>                       <key>public.filename-extension</key>
>                       <array>
>                               <string>cxtf</string>
>                       </array>
>               </dict>
>       </dict>
> </array>
> </plist>
> 
> 
> 
> If I force the above NSDocumentController method to return the expected UTI, 
> it does go ahead and opens the file properly. However, this is not a fix, 
> because it only allows the file to be opened by forcing it open with the app 
> and double-clicking, not in the Open dialog.
> 
> Still stumped, but maybe somone can spot an issue with the UTI export?
> 
> --Graham
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/franz%40ergosign.de
> 
> This email sent to fr...@ergosign.de


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to