ActivityResultFragmentVersionDetector uses an API that breaks in Lint 27.1.0+ (AGP 4.1.0+) [162155191]

Fixed

Bug

Status Update

No update yet.

Description

za...@gmail.com

created issue #1

Jul 26, 2020 07:08AM

Component used: Fragment
Version used: 1.3.0-alpha07
Devices/Android versions reproduced on: N/A

This code snippet will no longer work with lint tools 27.1.0+ (which is what's used in AGP 4.1.0+).

https://github.com/androidx/androidx/blob/c5ff35e40fbf353262ac22013e8c16e45b9017a3/activity/activity-lint/src/main/java/androidx/activity/lint/ActivityResultFragmentVersionDetector.kt#L97

It looks like it should be changed to buildVariant, and then there are changed APIs for accessing library info (the .libraries call at the end will also need fixing).

This results in the following failure when I build with newer lint tools and AGP 4.1.0-beta05 in our project

NoSuchMethodError:ActivityResultFragmentVersionDetector.checkDslPropertyAssignment(ActivityResultFragmentVersionDetector.kt:97)←Detector.checkDslPropertyAssignment(Detector.kt:418)←UastGradleVisitor.handleMethodCall(UastGradleVisitor.kt:190)←UastGradleVisitor.access$handleMethodCall(UastGradleVisitor.kt:34)←UastGradleVisitor$visitBuildScript$1.visitCallExpression(UastGradleVisitor.kt:40)←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:205)←ImplementationUtilsKt.acceptList(implementationUtils.kt:23)←UBlockExpression$DefaultImpls.accept(UBlockExpression.kt:21)

Sun Jul 26 2020 03:07:28 GMT-0400 (Eastern Daylight Time).png

23 KB

View

Download

Comments

il...@google.com <il...@google.com> #2Jul 26, 2020 11:28PM

For more information also see:

http://www.reddit.com/r/Android/comments/2me1m8/serious_memory_leak_in_android_lollipop/

https://www.reddit.com/r/Android/comments/2jwi5x/memory_leak_on_lollipop_if_background_apps_are/

my...@gmail.com <my...@gmail.com> #3Jul 27, 2020 09:28PM

[Comment deleted]

jb...@google.com <jb...@google.com> Jul 30, 2020 10:34PM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #4Jul 31, 2020 05:51PM

[Comment deleted]

ap...@google.com <ap...@google.com> #5Jul 31, 2020 11:57PM

I think, we have same problems.

https://code.google.com/p/android/issues/detail?id=79897

ap...@google.com <ap...@google.com> #6Jul 31, 2020 11:58PM

Happens every time I return to homescreen on Nexus 5.

jb...@google.com <jb...@google.com> #7Aug 12, 2020 02:30AM

Marked as fixed.

This is a real problem. As the hours pass system ram consumed gets bigger and bigger. It gets to the point that I have to reboot my device because apps keep reloading and sometimes even the launcher has to reload.It is a serious issue. I have to reboot daily

ap...@google.com <ap...@google.com> #8Dec 21, 2023 05:34PM

When play music crashed in the background today, with maps navigation running in the forefront, system ram usage was at 780mb. Maps ram usage was at 280mb. The play music process was stuck in "restarting" status until I swiped it out of recents and restarted it. This was after around 48 hours uptime. Camera app also started crashing mid-photosphere shortly after this. After a reboot system usage dropped to ~380mb and everything's working fine again.