I filed FB long time ago and didn't get as thourough response as LeadNav, just "Fix it yourself" resolution. But are you still having a problem? I have not had a single customer complaint since I've merged a range of suggestions in this thread together for my apps. Given response that LeadNav has got, it all makes some weird sense. I use "All files":
<dict>
<key>CFBundleTypeName</key>
<string>All files</string>
<key>CFBundleTypeRole</key>
<string>Viewer</string>
<key>LSHandlerRank</key>
<string>Alternate</string>
<key>LSItemContentTypes</key>
<array>
<string>public.content</string>
<string>public.data</string>
</array>
</dict>
As the last entry in document types. Above this I have the following for kmz:
<dict>
<key>CFBundleTypeIconFiles</key>
<array/>
<key>CFBundleTypeName</key>
<string>KMZ Google Earth</string>
<key>LSHandlerRank</key>
<string>Alternate</string>
<key>LSItemContentTypes</key>
<array>
<string>$(PRODUCT_BUNDLE_IDENTIFIER).kmz</string>
<string>public.archive</string>
<string>public.data</string>
</array>
</dict>
Then I have the following for the kmz in the Exported UTIs:
<dict>
<key>UTTypeConformsTo</key>
<array>
<string>public.data</string>
<string>public.archive</string>
</array>
<key>UTTypeDescription</key>
<string>KMZ Google Earth</string>
<key>UTTypeIdentifier</key>
<string>$(PRODUCT_BUNDLE_IDENTIFIER).kmz</string>
<key>UTTypeTagSpecification</key>
<dict>
<key>public.filename-extension</key>
<array>
<string>kmz</string>
<string>KMZ</string>
</array>
</dict>
</dict>
I have no intent to be adding anything for GPX right now, but I think I could do it in the same way as it is done for kmz. The only benefit that I'd see from adding GPX would be gpx file icons being my app icon sometimes?
I tested this with my own apps (compass 55, speedometer 55, planimeter 55) and they were never competing on any types (I do declare explicitely .sqlitedb, .mbtiles, .kmz and my own .trk) and I think they are not breaking other apps as well.
This led me to having no imported types. Will I need to agree with 1 million devs to have working imported types again? Per Apple's response to LeadNav, yes?
My understanding of this is that for the imported types, instead of merging info from different devs on it, Apple simply overrwites it in iOS 13? Imported types are not owned by the app. Next app comes and becomes the "master" over this imported UTI. If both matched perfectly on UTI there would no conflict?
Exported types are owned by the app. Looks to me that Apple still continues to merge information from the Exported UTIs in iOS 13.
I might be very wrong with my understanding, I hope not, but let me share it here in hope that someone wiser may comment. The solution seems to work, and while not being perfect, I can't suggest my customers to delete other apps (and which ones)? I believe this solution breaks nothing in fellow dev apps and makes my apps immune. I don't think that Apple is right with their new approach to the imported UTIs in iOS 13.