DexingFileDependenciesTask.outputKeepRules is a directory but is marked as an OutputFile [266780231]

Fixed

Bug

Status Update

No update yet.

Description

de...@squareup.com

created issue #1

Jan 26, 2023 05:20PM

DESCRIBE THE ISSUE IN DETAIL:

In AGP 7.4+, the outputKeepRules property in DexingFileDependenciesTask was changed from a RegularFileProperty to a DirectoryProperty (in this commit), however it is still marked as an OutputFile.

This causes a configuration error as gradle expects this property to be a file, but finds a directory instead. It should be marked with `OutputDirectory.

Configuration error:

org.gradle.internal.execution.WorkValidationException: A problem was found with the configuration of task ':app:desugarProductionReleaseFileDependencies' (type 'DexFileDependenciesTask').
  - In plugin 'com.android.internal.version-check' type 'com.android.build.gradle.internal.tasks.DexFileDependenciesTask' property 'outputKeepRules' is not writable because '[...]/app/build/intermediates/desugar_lib_external_file_lib_keep_rules/productionRelease' is not a file.
    
    Reason: Cannot write a file to a location pointing at a directory.
    
    Possible solutions:
      1. Configure 'outputKeepRules' to point to a file, not a directory.
      2. Annotate 'outputKeepRules' with @OutputDirectory instead of @OutputFiles.

This property appears to have been removed in AGP 8.1, but this issue still affects both AGP 7.4 and 8.0.

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: --
Version of Gradle Plugin: 7.4, 8.0-beta02
Version of Gradle: 7.6
Version of Java: --
OS: --

Comments

hu...@google.com <hu...@google.com> Jan 26, 2023 06:46PM

Assigned to an...@google.com.

bi...@google.com <bi...@google.com> Jan 26, 2023 06:53PM

Accepted by bi...@google.com.

bi...@google.com <bi...@google.com> #2Jan 26, 2023 07:58PM

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

de...@squareup.com <de...@squareup.com> #3Jan 26, 2023 08:14PM

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.

bi...@google.com <bi...@google.com> #4Feb 2, 2023 01:10AM

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"

bi...@google.com <bi...@google.com> #5Feb 2, 2023 07:13PM

Marked as fixed.

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

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

eb...@netflix.com <eb...@netflix.com> #6Feb 16, 2023 09:40PM

+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