Your solution was a great help, as I faced the same problem. But in my case at least, I was able to find a more elegant fix. It appears that iOS 13 is much more picky about UTI conformance lists than previous iOSes were.
I have a custom UTTypeDescription, which declares conformance to these UTIs:
public.color-lookup-table
public.3d-color-lookup-table
That worked fine up through iOS 12; my app showed up in the share sheet for the appropriate file type (a .cube file). But in iOS 13, the app didn't appear. Adding the "Unknown File" bundle type made it appear, but for every file type, not just the ones I wanted.
Prowling through https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/understanding_utis/understand_utis_declare/understand_utis_declare.html#//apple_ref/doc/uid/TP40001319-CH204-SW1
I saw this (emphasis added):
"Be sure to add conformance information if your proprietary type is a subtype of one or more existing types. In most cases you should not specify conformance to a nonpublic type, unless you are also declaring that type in your bundle. Although a custom UTI can conform to any UTI,
public.data
or
com.apple.package
must be at the root of the conformance hierarchy for all custom UTIs that are file formats (such as documents); otherwise, the system can’t tell if an item on disk has that UTI."
So I added public.plain-text to my list of UTIs, based on the hierarchy at: https://github.com/videovillage/LUTSpec/blob/master/LUTSPEC_UTI.md
public.plain-text
public.color-lookup-table
public.3d-color-lookup-table
That worked, but with the wrong icon; so I added public.data:
public.data
public.plain-text
public.color-lookup-table
public.3d-color-lookup-table
Now my app appears in the share sheets for .cube files, and only .cube files, and it has the right icon associated with it. (Well, on iOS 13. On an iOS 12 iPad, it shows the Numbers icon; on an iOS 12 iPhone SE it uses the Pages icon. But I've found that data-file icons on iOS tend to vary semi-randomly for no obvious reason, so I'm not as worried about this as I used to be!)
So make sure that your custom UTIs (if any) trace their conformance back to known Apple types, and you may be able to displence with the catch-all "unknown file" bundle type.