diff options
| author | Joanne Chung <joannechung@google.com> | 2020-11-03 23:48:25 +0800 |
|---|---|---|
| committer | Joanne Chung <joannechung@google.com> | 2020-11-09 18:53:35 +0800 |
| commit | 5b5f1c0acbe7c6f1b02731f46f0d2817bfd42b62 (patch) | |
| tree | 55f22a256eaff3dc6d3895854cd55e9209c24a24 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | dae90d760d0132f5d396bf4a7c00624e09f2edb0 (diff) | |
Use the flag FLAG_MUTABLE when creating the PendingIntent
Starting with S, any app targeting S+ will need to specify
explicitly either FLAG_MUTABLE or FLAG_IMMUTABLE when creating
PendingIntents.
This change helps mitigate against implicit PendingIntent reuse.
At present, all PendingIntents are mutable by default unless
FLAG_IMMUTABLE is explicitly set when creating them. This often
leads to developers accidentally making the PendingIntents mutable
and thus handing their receivers powers to fill in critical fields.
Because the autofill saveui retore mechanism will need to update it,
the PendingIntent should be mutable.
Bug: 170771150
Test: atest CtsAutoFillServiceTestCases
Test: Manual. Make sure the function works normal.
Test: Don't see PendingIntent error log.
Change-Id: I6e03a48968b98dec10e9c9dc05d1f3af42f8f0e5
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions