How to register iOS app to support OPML file type?

How to register an app to handle .opml file type? This is what I've tried adding to Info.plist file

<key>CFBundleDocumentTypes</key>

<array>

    <dict>

        <key>CFBundleTypeIconFiles</key>

        <array/>

        <key>CFBundleTypeName</key>

        <string>OPML</string>

        <key>LSHandlerRank</key>

        <string>Alternate</string>

        <key>LSItemContentTypes</key>

        <array>

            <string>public.opml</string>

            <string>org.opml.opml</string>

            <string>net.multimarkdown.opml</string>

            <string>com.apple.news.opml</string>

        </array>

    </dict>

</array>

With keys defined above when .opml file is opened via "Open in ..." app does not show up in the list of apps that can handle this file type.

I've noticed that if public.data is added in the LSItemContentTypes array it does show the app in the "Open in..." list but app is shown for all other undesirable file types. Is there a specific content type that is missing?

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

1

You are not exporting your file type. This is not a standard file type known to the system, so if you don't export it, the system can't see it as a public type.

– matt
Jan 1 at 23:03

Try adding entries to the Imported Type Declarations for the OPML related UTIs.

– rmaddy
Jan 1 at 23:03

@matt indeed that was the issue, thank you for the hint!

– Digitech
Jan 2 at 3:12

Cool, I'll add that as an answer.

– matt
Jan 2 at 3:15

add a comment |

How to register an app to handle .opml file type? This is what I've tried adding to Info.plist file

<key>CFBundleDocumentTypes</key>

<array>

    <dict>

        <key>CFBundleTypeIconFiles</key>

        <array/>

        <key>CFBundleTypeName</key>

        <string>OPML</string>

        <key>LSHandlerRank</key>

        <string>Alternate</string>

        <key>LSItemContentTypes</key>

        <array>

            <string>public.opml</string>

            <string>org.opml.opml</string>

            <string>net.multimarkdown.opml</string>

            <string>com.apple.news.opml</string>

        </array>

    </dict>

</array>

With keys defined above when .opml file is opened via "Open in ..." app does not show up in the list of apps that can handle this file type.

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

1

You are not exporting your file type. This is not a standard file type known to the system, so if you don't export it, the system can't see it as a public type.

– matt
Jan 1 at 23:03

Try adding entries to the Imported Type Declarations for the OPML related UTIs.

– rmaddy
Jan 1 at 23:03

@matt indeed that was the issue, thank you for the hint!

– Digitech
Jan 2 at 3:12

Cool, I'll add that as an answer.

– matt
Jan 2 at 3:15

add a comment |

How to register an app to handle .opml file type? This is what I've tried adding to Info.plist file

<key>CFBundleDocumentTypes</key>

<array>

    <dict>

        <key>CFBundleTypeIconFiles</key>

        <array/>

        <key>CFBundleTypeName</key>

        <string>OPML</string>

        <key>LSHandlerRank</key>

        <string>Alternate</string>

        <key>LSItemContentTypes</key>

        <array>

            <string>public.opml</string>

            <string>org.opml.opml</string>

            <string>net.multimarkdown.opml</string>

            <string>com.apple.news.opml</string>

        </array>

    </dict>

</array>

With keys defined above when .opml file is opened via "Open in ..." app does not show up in the list of apps that can handle this file type.

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

How to register an app to handle .opml file type? This is what I've tried adding to Info.plist file

<key>CFBundleDocumentTypes</key>

<array>

    <dict>

        <key>CFBundleTypeIconFiles</key>

        <array/>

        <key>CFBundleTypeName</key>

        <string>OPML</string>

        <key>LSHandlerRank</key>

        <string>Alternate</string>

        <key>LSItemContentTypes</key>

        <array>

            <string>public.opml</string>

            <string>org.opml.opml</string>

            <string>net.multimarkdown.opml</string>

            <string>com.apple.news.opml</string>

        </array>

    </dict>

</array>

With keys defined above when .opml file is opened via "Open in ..." app does not show up in the list of apps that can handle this file type.

ios opml

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

edited Jan 1 at 22:58

rmaddy

245k27324387

edited Jan 1 at 22:58

rmaddy

245k27324387

edited Jan 1 at 22:58

rmaddy

245k27324387

asked Jan 1 at 22:50

Digitech

1628

asked Jan 1 at 22:50

Digitech

1628

asked Jan 1 at 22:50

Digitech

1628

1

You are not exporting your file type. This is not a standard file type known to the system, so if you don't export it, the system can't see it as a public type.

– matt
Jan 1 at 23:03

Try adding entries to the Imported Type Declarations for the OPML related UTIs.

– rmaddy
Jan 1 at 23:03

@matt indeed that was the issue, thank you for the hint!

– Digitech
Jan 2 at 3:12

Cool, I'll add that as an answer.

– matt
Jan 2 at 3:15

add a comment |

1

You are not exporting your file type. This is not a standard file type known to the system, so if you don't export it, the system can't see it as a public type.

– matt
Jan 1 at 23:03

Try adding entries to the Imported Type Declarations for the OPML related UTIs.

– rmaddy
Jan 1 at 23:03

@matt indeed that was the issue, thank you for the hint!

– Digitech
Jan 2 at 3:12

Cool, I'll add that as an answer.

– matt
Jan 2 at 3:15

You are not exporting your file type. This is not a standard file type known to the system, so if you don't export it, the system can't see it as a public type.

– matt
Jan 1 at 23:03

Try adding entries to the Imported Type Declarations for the OPML related UTIs.

– rmaddy
Jan 1 at 23:03

@matt indeed that was the issue, thank you for the hint!

– Digitech
Jan 2 at 3:12

Cool, I'll add that as an answer.

– matt
Jan 2 at 3:15

add a comment |

1 Answer
1

active

oldest

votes

You are declaring a file type, but that type is not a built-in known type (such as PDF), and you yourself are not exporting that type; therefore it is not seen by the runtime as publicly available to other apps.

answered Jan 2 at 3:17

matt

331k46541739

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

1

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

2

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999553%2fhow-to-register-ios-app-to-support-opml-file-type%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

answered Jan 2 at 3:17

matt

331k46541739

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

1

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

2

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

add a comment |

answered Jan 2 at 3:17

matt

331k46541739

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

1

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

2

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

add a comment |

answered Jan 2 at 3:17

matt

331k46541739

answered Jan 2 at 3:17

matt

331k46541739

answered Jan 2 at 3:17

matt

331k46541739

answered Jan 2 at 3:17

matt

331k46541739

answered Jan 2 at 3:17

matt

331k46541739

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

1

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

2

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

add a comment |

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

1

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

2

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

While it works either way, I would choose to put these under Imported type declarations and not Exported type declarations. I use Exported type declarations for new UTIs invented by my app. I use Imported type declarations for non-publicly available declarations that are not specific to my own app. These OPML UTIs are not unique to this person's app. Functionally it doesn't matter but it's a way to organize UTI declarations.

– rmaddy
Jan 2 at 15:47

Can you edit my answer to be more accurate?

– matt
Jan 2 at 16:13

Found a technical note on this topic https://developer.apple.com/library/archive/qa/qa1587/_index.html for the custom document type, or a document type that iOS does not already know about, they recommend to use exported UTI. But to keep UTI declarations organized following convention @rmaddy suggested makes a lot of sense to me

– Digitech
Jan 5 at 18:44

@Digitech What 'Identifier' / 'Comforms To' values did you use in the "Imported UTIs" Section to get OPML files to be imported?

– Emmett Harper
Feb 27 at 7:47

@EmmettHarper Identifier public.opml Confirms To public.data

– Digitech
Feb 27 at 17:07

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu