Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

App Store Connect Warns - Invalid Document Configuration

I have submitted a Single View Swift iOS application to App Store Connect. The application is not Document Based.

The application uploads successfully, but I get the following warning in an email from Apple. I can still test the application through Test Flight, but I want to eliminate the warning.

"Invalid Document Configuration - Document Based Apps should support either the Document Browser (UISupportsDocumentBrowser = YES) or implement Open In Place (LSSupportsOpeningDocumentsInPlace = YES/NO)."

like image 353
Jared Barden Avatar asked Sep 07 '18 18:09

Jared Barden


People also ask

How do I connect to the App Store Connect?

Sign in to your Apple Search Ads Basic account to go to your dashboard. Click the Edit Linked Accounts link in the upper-right corner. Select the App Store Connect accounts you want to link or unlink. Click Save.

How do you download an app from App Store Connect?

From Users and Access, click Keys. The page opens with App Store Connect API selected. Navigate to an API key under the Active section, then click Download API Key for the key you want to download. In the dialog, click Download.


Video Answer


1 Answers

I just ran into the same problem; I don't know why, since I barely change anything since the previous version of my app.

Anyway, my app doesn't support the Document Browser, so the first half of the error message doesn't apply. That left me with the second half. I looked up LSSupportsOpeningDocumentsInPlace's documentation and still wasn't clear on how it works, so I decided to try both options. My app supports it's own document type, and when a user opens an appropriate file iOS shows an action sheet with the option "Copy to Leio" (my app). After setting LSSupportsOpeningDocumentsInPlace to YES, iOS wouldn't show that action sheet anymore; it would just open my app and do nothing. So I set it to NO; now the app works as it did before and I'm not getting that error message anymore. If you don't handle any document types I suppose you could set the option either way.


Edit: There's some more information about that option here.

So there you go. If your app were to edit a document, would it edit the original document, or would it make a copy and deal with that? Set the option accordingly. If you really don't do anything like that I'd guess setting the option to NO would be the safest bet, and I think that's how my app behaved when I hadn't set that option at all.

like image 189
dbmrq Avatar answered Oct 13 '22 22:10

dbmrq