/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14567 /home/runner/work/_temp/codeql_databases/java
CodeQL detected code written in Java/Kotlin and Java/Kotlin but could not process any of it. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build .
Error: Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14567 /home/runner/work/_temp/codeql_databases/java". Exit code was 32 and last log line was: CodeQL detected code written in Java/Kotlin and Java/Kotlin but could not process any of it. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.
We should find out why and fix it. We could also update dependencies in the same run.
[x] Update dependencies, including Kotlin, AGP and gradle
[ ] Find out why CodeQL fails and fix it
I'd remove the --no-daemon call in the CodeQL CI, because its not necessary
Maybe autobuild works in the meanwhile, then we wouldn't need gradle assemble. Otherwise keep the assemble task.
For some reason, CodeQL currently fails:
We should find out why and fix it. We could also update dependencies in the same run.
--no-daemoncall in the CodeQL CI, because its not necessarygradle assemble. Otherwise keep the assemble task.