android:exported needs to be explicitly specified for <activity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` [261013909]

Infeasible

Bug

Status Update

No update yet.

Description

cr...@gmail.com

created issue #1

Dec 1, 2022 02:52PM

Component used: androidx.arch.core:core-runtime
Version used: 2.1.0
Devices/Android versions reproduced on:

If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).

Is this library not updated to meet the Play Store's new requirement of target Android 12?
Android Studio is throwing the `android:exported` issue on this library.

(

https://developer.android.com/google/play/requirements/target-sdk)

```
2022-12-01T09:33:06.269-0500 [INFO] [com.android.build.gradle.tasks.ProcessApplicationManifest] Merging manifest with lower [androidx.arch.core:core-runtime:2.1.0] AndroidManifest.xml:17:1-24:12
2022-12-01T09:33:06.270-0500 [INFO] [com.android.build.gradle.tasks.ProcessApplicationManifest] uses-sdk defined in both files...
2022-12-01T09:33:06.270-0500 [INFO] [com.android.build.gradle.tasks.ProcessApplicationManifest] Merging uses-sdk with lower [androidx.arch.core:core-runtime:2.1.0] AndroidManifest.xml:20:5-22:41
2022-12-01T09:33:06.271-0500 [INFO] [com.android.build.gradle.tasks.ProcessApplicationManifest] Merging result: ERROR
2022-12-01T09:33:06.271-0500 [ERROR] [com.android.build.gradle.tasks.ProcessApplicationManifest] /Users/andre/git/alliance-customer-app-android/app/src/main/AndroidManifest.xml Error:
android:exported needs to be explicitly specified for <activity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See

https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

```

Comments

il...@google.com <il...@google.com> #2Dec 1, 2022 05:47PM

Status: Won't Fix (Infeasible)

This was partially addressed by

https://android-review.googlesource.com/c/platform/frameworks/support/+/2076902, available now in 1.1 RC02, see

b/230665435

. As compilation on user builds requires a full target reinstall (which is a behavior change), we offer an opt out, which can be used to accomplish this feature request: 1) configure every macrobench to use `CompilationMode.Full()` 1) manually issuing the compile command `cmd package compile -f -m speed <packagename>` for your target 1) pass the instrumentation arg `androidx.benchmark.compilation.enable` = `false` to skip compilation/reinstall for each macrobenchmark. This should still give you the numbers you've been seeing, while avoiding the cost of a large AOT each test. Leaving this bug open, since in general we should be able to do this more automatically for everything without warmup driven profiles. (Somewhat related bug - there have been excess compilations issued specifically for `Compilation.None`, `StartupMode.COLD` benchmarks, which has been fixed, but not shipped publicly yet:

b/231976084

)

Issue 261013909

Description

Issue summary

Comments

il...@google.com <il...@google.com> #2Dec 1, 2022 05:47PM

Add comment

Issue metadata