NullSafeMutableLiveData lint doesn't work when field have modifiers [183696616]

Fixed

Bug

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Mar 25, 2021 02:14PM

Component used:
Version used: 2.3.1

```
class MyClass {
internal val liveDataField = MutableLiveData<Boolean>()

fun foo() {
liveDataField.value = false
liveDataField.value = null
}
}
```

Comments

se...@google.com <se...@google.com> Mar 25, 2021 02:23PM

Reassigned to jb...@google.com.

ma...@gmail.com <ma...@gmail.com> #2Mar 25, 2021 03:17PM

fix:

https://github.com/androidx/androidx/pull/147

ap...@google.com <ap...@google.com> #3Mar 30, 2021 10:47AM

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-main

commit 428f0ec685ff80035c0511c0cdb12b9770b6159c
Author: Maxim Savoskin <maximsavoskin@gmail.com>
Date: Mon Mar 29 13:20:52 2021

[GH] [Lifecycle] [Lint] fixes

b/183696616

: KtCallExpression is not always the first in the list

## Proposed Changes
KtCallExpression is not always the first in the list. In this case, it is KtModifierList.

## Testing

Test: ./gradlew test lint buildOnServer

## Issues Fixed

Fixes:

https://issuetracker.google.com/issues/183696616

This is an imported pull request from

https://github.com/androidx/androidx/pull/147.

Resolves #147
Github-Pr-Head-Sha: 3c2693e2f4cceb367c9c169749d1391a9da2740f
GitOrigin-RevId: a6440720029b1c0c702207f1393d3b01180691b8
Change-Id: I9b4383329b9ece85e3bffa4a9bf8e8a3f0c3d84a

M lifecycle/lifecycle-livedata-core-ktx-lint/src/main/java/androidx/lifecycle/lint/NonNullableMutableLiveDataDetector.kt
M lifecycle/lifecycle-livedata-core-ktx-lint/src/test/java/androidx/lifecycle/lint/NonNullableMutableLiveDataDetectorTest.kt

https://android-review.googlesource.com/1656820

mi...@gmail.com <mi...@gmail.com> #4Apr 2, 2021 03:28AM

Will you guys be releasing a hot fix 2.3.2 for this?

mi...@gmail.com <mi...@gmail.com> #5Apr 12, 2021 10:58PM

Any updates about when this is going live?

mi...@gmail.com <mi...@gmail.com> #6Jun 2, 2021 02:24AM

Hi, I hate to keep posting same comments, but are there any plans to release this fix? It's blocking us from updating to fragment 1.3.2+.

ja...@gmail.com <ja...@gmail.com> #7Feb 23, 2022 05:25AM

c0...@gmail.com <c0...@gmail.com> #8May 16, 2022 03:50AM

How do you update components that are viewed through the chrome.url page of they all indicate that they are not up to date

c0...@gmail.com <c0...@gmail.com> #9May 16, 2022 03:52AM

Also my phone was in the hands of a skilled IT individual, how can I verify what, if any, modifications took place. I cannot enter recovery mode on my device....