commit | 0511077086852d8b987e70eb57ab30dfc0148a7b | [log] [tgz] |
---|---|---|
author | Mark Renouf <mrenouf@google.com> | Tue Feb 20 09:49:03 2024 -0500 |
committer | Mark Renouf <mrenouf@google.com> | Tue Feb 20 15:36:42 2024 +0000 |
tree | d8e9f33eff023cbf6bc1aa032a4f5ab336e78c2a | |
parent | cb295796fbbcb96686475f7631a029209d2d9474 [diff] |
Check for EXTRA_CHOOSER_RESULT for backcompat until V2 is released This keeps the existing functionality working in V1, with the flag enabled for apps using Intent.createChooser which will begin sending the new extra value. The extra used has no bearing on functionality. With the feature flag disabled, the same functionality continues while also accepting the the extra name from Intent.createChooser. Without this, apps using Intent.createChooser will stop receiving results with the flag[1] disabled. [1] intentresolver/com.android.intentresolver.modular_framework Bug: 325545074 Test: atest android.content.cts.IntentTest#testCreateChooser Change-Id: Id25de6410835a85e71cb58277015d8ede51f4e4d
IntentResolver
provides the implementation for Intent ACTION_CHOOSER
See also: ShareCompat.IntentBuilder