Fixed
Status Update
No update yet.
Comments
ra...@google.com
ra...@google.com
Using navigation version 2.6.0 and 2.7.1 the issue still persists.
After further investigation, the behaviour can be corrected by filtering on backstack entries where current state is at least started. In my opinion the name visibleEntries is misleading if it contains entries that are not actually visible or in transition.
ap...@google.com
Note that as per the visibleEntries documentationCREATED state - those are the entries that are in the process of being removed (i.e., they are no longer in the back stack, but have not yet marked their transition as complete).
It is a bug that those entries aren't removed when their exit animation completes and that's what we'll be looking into.
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