Invalid Document Configuration

Question

Created Sep ’18

Replies 5

Boosts 0

Views 3.6k

Participants 5

Hi,

I'm updating my app to include some new features. The app really has nothing to do with document support but when I uploaded a recent version for testing, I got an email indicating that there were some issues with the delivery; namely,

Invalid Document Configuration - Document Based Apps should support either the Document Browser (UISupportsDocumentBrowser = YES) or implement Open In Place (LSSupportsOpeningDocumentsInPlace = YES/NO). Visit https://developer.apple.com/document-based-apps/ for more information.

After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.

I re-built the app, uploaded it again and got the same email. Like I said, my app doesn't deal with documents and I don't show use of those keys anywhere.

Why am I getting this message? What do I need to do to corret the situation?

Thaks,

Ramon.

Boost

Answer 1

landymagma7 OP

Sep ’18

Same here. Since my previous upload, I have only added the minimum FireBase & Firebase Messaging frameworks, after finding out that Fabric's going to get closed next year after Crashlytics fully migrates to FireBase.

Maybe it's something buried in Google's mess.

0

Answer 2

landymagma7 OP

Sep ’18

One other thought is that we have (for the last 7 years) enabled file sharing so that the configuration of our iOS app can be delivered via iTunes rather than requiring a live internet connection and potentially multi-gigabyte data transfer. Even though we've added no other flagging or functionlity to do with file or document sharing/browsing, maybe that's now set off some new warning flag up in Apple-land.

0

Answer 3

5tan_A100 OP

Sep ’18

I'm getting the same error and I'm only doing a simple code-free, sticker pack. I don't get what document configuration or access will my sticker be gaining, there's no reading or writing of any information. Not sure what to do.

0

Answer 4

lammertw OP

Sep ’18

We're also seeing this issue. But only with about half of our builds. We have a continuous integration system so every commit is submitted to App Store Connect and with random builds we're getting this reported as an issue while only some unrelated code was changed. So seems like an App Store Connect problem to me.

0

Answer 5

hishak OP

Sep ’18

I removed

CFBundleDocumentTypes
in my apps

Info.plist (

even though the array was empty). My app doesn't support any document types. Removing that key removed the warning for me when I re-build and re-submitted to iTunes Connect.

0