Status Update
No update yet.
Comments
ra...@google.com
ra...@google.com
From the other issue:
note that it is never the right approach to attach a
<deeplink>to an<activity>destination as that will never give you the right behavior when using anon another app's task (where the system back should immediately take the user back to the app that triggered your deep link). Instead, you should attach your deep link directly to your second activity (either by manually writing the appropriate implicit deep link <intent-filter>or by adding the<deeplink>to the start destination of a nav host in that second activity).
A lint error saying as such when a <deepLink> element is added in Navigation XML would go a really long way to avoiding this case. Our navigation-runtime-lint artifact that would contain this check.
ap...@google.com
We have some
Description
android.arch.work:work-runtime-ktx:1.0.0-alpha06
Version used:
Theme used: N/A
Devices/Android versions reproduced on: All
- Relevant code to trigger the issue.
class SomeWorker: Worker() {
fun doWork() {
val input = inputData.getIntArray("key")
if( input == null || input.isEmpty() ) {
// work
}
}
}
there is a lint warning on "input == null" saying it is always false. This is because the return type is annotated with @NonNull. The javadoc and code clearly say/show that null can be returned.
The same holds true for getBooleanArray(String)
- A screenrecord or screenshots showing the issue (if UI related).
N/A