Script deploy-hilt.sh fails

[quiro91]

Running the script:

./util/deploy-hilt.sh  install:install-file LOCAL-SNAPSHOT

fails with the following error:

ERROR: /Users/lorenzo/projects/dagger/java/dagger/hilt/android/processor/BUILD:39:1: error executing shell command: '/bin/bash -c 
  JAVA_HOME="$(cd "external/local_jdk" && pwd)" # this is used outside of the root

  TMPDIR=$(mktemp -d)
  for jar in bazel-out/darwin-fastbuild/bin/java/dagger/hilt/android/processo...' failed (Exit 1) bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
Error: duplicate files in merged jar: META-INF/gradle/incremental.annotation.processors~5
META-INF/gradle/incremental.annotation.processors~2
META-INF/gradle/incremental.annotation.processors~3
META-INF/gradle/incremental.annotation.processors~4
META-INF/gradle/incremental.annotation.processors~1
META-INF/gradle/incremental.annotation.processors~6
META-INF/gradle/incremental.annotation.processors~7
META-INF/gradle/incremental.annotation.processors~
META-INF/services/javax.annotation.processing.Processor~7
META-INF/services/javax.annotation.processing.Processor~6
META-INF/services/javax.annotation.processing.Processor~1
META-INF/services/javax.annotation.processing.Processor~
META-INF/services/javax.annotation.processing.Processor~4
META-INF/services/javax.annotation.processing.Processor~3
META-INF/services/javax.annotation.processing.Processor~2
META-INF/services/javax.annotation.processing.Processor~5
INFO: Elapsed time: 0.391s, Critical Path: 0.29s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

[danysantiago]

Are you on Mac OS?

I think this was my fault (sorry!), caused by the changes here: google/bazel-common@bf87eb1. I believe the find between Mac (BSD version) and Linux (GNU version) differ in the supported regex syntax.

[quiro91]

Yes, I am on MacOS. Ah, interesting, didn't know that :)

[kokeroulis]

I am facing the same issue here. Yes i am on MacOS too... Is there any workaround around this?