Fix shouldShowRequestPermissionRationale causing memory leak in Andro…#435
Fix shouldShowRequestPermissionRationale causing memory leak in Andro…#435alanv merged 6 commits intoandroidx:androidx-mainfrom
Conversation
|
Presubmit is unhappy because there's no Please update your PR message to use |
|
@alanv Thanks for the reminder, the revision has been completed |
|
Still needs a |
@alanv Hello, I have made the modification here as required. |
|
@tikurahul @alanv @liutikas Hello, this problem seems to be difficult to solve, do I need to initiate a new pull request? |
|
If @dlam and @tikurahul can't get this working, our GitHub workflow is busted. Let's keep pushing on this PR. |
|
I added some additional logging in the |
…ts and optimized code logic
…-leak # Conflicts: # core/core/src/main/java/androidx/core/app/ActivityCompat.java
|
@tikurahul Hello, I have modified the commit message as required, can you take a look again? |
|
Kicking off another workflow run ! It moved past the point of last failure. So its promising 🤞🏽 |
|
@tikurahul Hello, I found a code check failure here, will this affect code merging? |
This is a real error that you need to fix. @alanv can probably advise on best way to go about it. |
|
@alanv Hello, do you have any good advice on this issue? |
|
@tikurahul @dlam @liutikas Do you guys have any good solutions? |
|
@alanv @tikurahul @dlam @liutikas Hi, I see |
Yes, this can be suppressed since the call site is wrapped with an SDK_INT check. |
|
@alanv Hello, I have submitted the modification of this part of the code |
|
@alanv Hello, please check whether there are any problems with the changes, if there are any, please point out, if not, please approve them |

Proposed Changes
Hello, there will be a memory leak when calling
activity.shouldShowRequestPermissionRationalein Android 12. The problem is fixed in Android 12L, but it is still a legacy in Android 12. It is recommended to reflect theapplication.shouldShowRequestPermissionRationalemethod to avoid this problem.Testing
Test: manually ran with LeakCanary
Please see
IssueTracker 212113500
IssueTracker 207946473
IssueTracker 204539732
Issues Fixed
Fixes: b/212113500
Fixes: b/207946473
Fixes: b/204539732