File Provider UI extension unsupported on Vision OS

Question

Created 3d

Replies 2

Boosts 0

Participants 2

I am building a Vision OS app that includes a File Provider and File Provider UI extension. Both work great in simulator.

When uploading to TestFlight, this message is shown:

Unsupported Platform. The extension bundle [...]/PlugIns/File ProviderUI.appex is not supported for this platform.

If I exclude the File Provider UI extension from the build, it is accepted. If I even include a hello-world File Provider UI extension, the error shown above is returned by ASC.

There is contradicting documentation on this subject:

https://developer.apple.com/documentation/technologyoverviews/app-extensions states that File Provider UI extension is not supported on Vision OS, so that explains ASC behavior
https://developer.apple.com/documentation/FileProviderUI (and all other framework docs) states that File Provider UI extension is supported on Vision OS, so that explains why it works on simulator.

Now, which of these two is correct?

My best guess at this point is that ASC's logic follows the first document linked above, while the OS and framework actually follow the second.

The same discrepancy seems to hold for macOS, but I'm currently focusing on Vision OS.

Ideas? Anybody using a File Provider UI extension on Vision OS?

Boost

Answer 1

DTS Engineer OP

Apple

2h

Thanks for reporting the discrepancy. Would you mind to file a feedback report for us and share your report ID here? I can file one as well, but you represent the developer community and, as an originator, you can get notified of the status change and follow up with it if that matters to you.

Regarding the following:

The same discrepancy seems to hold for macOS, but I'm currently focusing on Vision OS.

Do you mean that uploading to TestFlight a macOS app with an NSFileProviderReplicatedExtension + a file provider UI extension triggers the same error? That will be an issue in the app submission process, because these extensions are supported on macOS, as discussed here.

I haven't had a chance to try on visionOS yet...

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

0

Answer 2

hekkihek OP

1h

Do you mean that uploading to TestFlight a macOS app with an NSFileProviderReplicatedExtension + a file provider UI extension triggers the same error? That will be an issue in the app submission process, because these extensions are supported on macOS, as discussed here.

I haven't tested this with macOS (yet). What I meant is that the two documents I listed before have the same contradiction for macOS as for visionOS.

I am not sure if the availability of the sample code makes it more official. I mean, that page lists Mac Catalyst as supported while FPUIActionExtensionViewController.h states

FPUI_AVAILABLE(ios(11.0), macos(10.15))
API_UNAVAILABLE(macCatalyst)

I'll probably try this for macOS at some point in the future as the app is also available on macOS (with NSFileProviderReplicatedExtension), but my current File Provider UI code is based on UIKit (coming from iOS) so that is why I started with visionOS. Which is not really encouraging yet :-)

From a developer's viewpoint the issue is pretty simple, as the full framework documentation lists visionOS as supported, and it works as expected in the simulator. It looks like just a flag at the App Store that is blocking the upload.

I remember facing a similar issue in the past with the App Store blocking a specific (legitimate) app type. I don't recall the exact details, maybe someone else recognizes this?

Anyway, I'll file the FB report as you requested.

Richard.

0