Fixed
Status Update
Comments
rk...@google.com <rk...@google.com>
tn...@google.com <tn...@google.com> #2
Information redacted by Android Beta Feedback.
an...@steadfastinnovation.com <an...@steadfastinnovation.com> #3
Thanks for reporting this issue. We have passed this to the development team and will update this issue with more information as it becomes available.
tn...@google.com <tn...@google.com> #5
Same here, need this feature.
tn...@google.com <tn...@google.com> #6
Same here on the Pixel 7a. I liked the feature and had been using it since it was added so I hope it's restored.
an...@google.com <an...@google.com> #7
Now fixed and works on my 6a.
Description
java.nio
APIs can be used below API 26 withcoreLibraryDesugaring "com.android.tools:desugar_jdk_libs_nio:2.1.3"
. However, as described in thejava.nio
customizations documentationFor example, running the following on API 21 produces a
java.lang.UnsupportedOperationException
:This is expected per the documentation, but is not discoverable except at runtime.
However, when using
coreLibraryDesugaring "com.android.tools:desugar_jdk_libs:2.1.3"
(the non-nio artifact), usages of this API (and all otherjava.nio
APIs) produce lint errors unless wrapped in checks for API 26+.Is it possible to show lint errors just for the APIs that will fail at runtime when they're not wrapped in API checks for API 26+ when using
desugar_jdk_libs_nio
? That way the build will fail rather than discovering this at runtime.