configureCMakeDebug flakily crashing with null pointer exception [255788407]

Fixed

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

Oct 26, 2022 05:46PM

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Run builds that include cmake in androidx

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test:integration-tests:junit-gtest-test:configureCMakeDebug[arm64-v8a]'.
Caused by: java.lang.NullPointerException
	at com.android.build.gradle.internal.cxx.configure.ConfigureInvalidationStateKt.createConfigurationInvalidationState(ConfigureInvalidationState.kt:88)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$invalidationState$1.invoke(ExternalNativeJsonGenerator.kt:168)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$invalidationState$1.invoke(ExternalNativeJsonGenerator.kt:167)
	at com.android.build.gradle.internal.cxx.timing.TimingEnvironmentKt.time(TimingEnvironment.kt:32)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configureOneAbi(ExternalNativeJsonGenerator.kt:167)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configure(ExternalNativeJsonGenerator.kt:103)
	at com.android.build.gradle.tasks.ExternalNativeBuildJsonTask.doTaskAction(ExternalNativeBuildJsonTask.kt:72)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:65)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask.taskAction(UnsafeOutputsTask.kt:63)
	at jdk.internal.reflect.GeneratedMethodAccessor1484.invoke(Unknown Source)

https://ci.android.com/builds/submitted/9220848/androidx_incremental/latest/view/logs/build_error.log

Studio Build: N/A Version of Gradle Plugin: 8.0.0-alpha05 Version of Gradle: 7.5 Version of Java: 17 OS: Linux

Comments

au...@google.com <au...@google.com> #2Oct 26, 2022 08:02PM

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ya...@google.com <ya...@google.com> Oct 26, 2022 08:23PM

Assigned to an...@google.com.

jo...@google.com <jo...@google.com> Oct 26, 2022 09:11PM

Reassigned to jo...@google.com.

jo...@google.com <jo...@google.com> #3Nov 4, 2022 09:01PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

je...@google.com <je...@google.com> #4Nov 11, 2022 07:21PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

jeff.gradle.log

67 KB

View

Download

jeff.nativeBuildStaging.zip

908 KB

Download

jo...@google.com <jo...@google.com> #5Nov 16, 2022 07:40PM

Marked as fixed.

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

je...@google.com <je...@google.com> #6Nov 23, 2022 05:20PM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found