IssueTracker

Take this code for example:

Uri uri=FileProvider.getUriForFile(mContext, BuildConfig.APPLICATION_ID + ".fileprovider", output);
Intent myIntent = new Intent(Intent.ACTION_VIEW, uri);
myIntent.setType("text/plain");
myIntent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
startActivity(myIntent);

This will cause problems for the *receiving* app, because setType() wipes out the Uri set in the constructor, and so the text editor app will get a null Uri and probably will not handle that especially well.

Ideally, there would be a Lint warning for this scenario: supplying a Uri to an Intent prior to a setType() call on that Intent. At present, neither Lint nor Android Studio inspections point out this problem. The recommended solution would be to use setDataAndType(), supplying the Uri and MIME type in one fell swoop.

(for whatever a "fell swoop" is...)

FWIW, the same basic issue was reported five years ago and was ignored for three years: https://issuetracker.google.com/issues/36967533.

Thanks for considering this!