Latest Android app breaks viewing log files

But I noticed this major change in behavior after upgrading to Dropbox 320, not after upgrading the OS so not sure how your explanation could apply.

Also not sure how MIME type comes into play. As I understand it, the Dropbox API doesn't support setting MIME type per file, so how do you determine the MIME type by file extension, by guessing? I don't understand what you mean by log files with incorrect MIME type? It's a text file, hence not possible to store MIME type in the file itself.

Here's what I see:

Dropbox 324.1.2 Android 12

1.1 Failure (should give me the opportunity to use Log Viewer or Dropbox Text Editor)

.bak
.cache
.conf
.deb
.downloaded

1.2 Success

.ini
.json
.m3u (had to reselect which app, had already done this prior to 320.2.10, not sure why I had to do that again)
.properties

1.3 Partial Success (opens in Dropbox Text Editor, doesn't allow to use Log Viewer or another relevant app)

.log
.sh
.txt
.xml

1.4 Inconsistent Behavior (opens in one viewer when "clicked", opens in another viewer via Open with..., yet doesn't allow selection of which app)

.css
.html

2. Binary

2.1 Failure (don't have viewers installed for these, so this is to be expected)

.db
.jar

2.2 Success

.ico
.png
.xlsx

The reason that you saw this after upgrading the Dropbox app is because we constantly have to upgrade the app to keep it up to date with new restrictions and policies put in place by the Android OS. So while you didn't upgrade your OS, the legacy way we were checking for apps that could open files was no longer supported on newer OS versions, so we had to update how we do things to ensure that it works for everyone.

As I mentioned, I've started discussions for this internally to look into how we can try to make this work more like it used to (while still being compatible with new Android versions).