If this is for your app you might want to define an EXPORTED type that wont conflict with an existing UTI (using a unique extension which can be about as long as you want)
I suspect that trying to use a UTI that is already defined to NOT have any extensions (its basically a superclass type) may relate
It seems a .db file is actually a public.data file instead of database, by changing UTI and Conforms parameters to public.data it works. No matter if declaring Exported or imported.
Not sure why it worked with previous versions of Xojo.
Anyway I’ll retry with new and longer extensions but I think they have to conform to public.data.
Public.database is a super type
Its in table 1 row 5
Now the fun part
Uti’s define two possible hierarchies
One LOGICAL
One PHYSICAL
Somewhere I have an image of all that UTI data which makes these two separate but related hierarchies more visible.
It worked with old versions because old versions used a different mechanism that is no longer supported (supposedly)
And older versions actually did it wrong in some spots so it may have looked like it was working BUT it would actually take over certain UTI’s (this was the case with PDF’s at one time)