I have a pipeline to build and distribute an android application. Previously i was getting success with the same bitbucket.yaml configuration but then it returns error to me. When it comes to the '''kaptReleaseKotlin''' task it is giving this error
```
> Task :app:kaptReleaseKotlin
line 1:30 token recognition error at: ''??'
line 1:34 token recognition error at: '''
line 1:94 token recognition error at: ''??'
line 1:98 token recognition error at: '''
line 1:57 token recognition error at: ''??'
line 1:61 token recognition error at: '''
line 1:52 token recognition error at: ''??'
line 1:56 token recognition error at: '''
line 1:100 token recognition error at: ''??'
line 1:104 token recognition error at: '''
```
First error message is
> Task :app:kaptReleaseKotlin FAILED
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:kaptReleaseKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptWithoutKotlincTask$KaptExecutionWorkAction
> java.lang.reflect.InvocationTargetException (no error message)
2: Task failed with an exception.
-----------
* What went wrong:
Configuration cache problems found in this build.
1 problem was found storing the configuration cache.
- Task `:app:collectReleaseDependencies` of type `com.android.build.gradle.internal.tasks.PerModuleReportDependenciesTask`: invocation of 'Task.project' at execution time is unsupported.
Adding -Dfile.encoding\=UTF-8 argument to jvmargs in gradle.properties solved my issue
org.gradle.jvmargs=-Xmx1536M -Dkotlin.daemon.jvm.options\="-Xmx1024M" -Dfile.encoding\=UTF-8
Hi @Eren Alpaslan and welcome to the community.
There are many possible causes for errors on builds that were previously successful, like changes in your code, changes in the Docker image used as a build container, third-party dependency changes.
You can check the following guide, specifically "Scenario 1: Builds were successful earlier, but started failing recently", for steps on how to troubleshoot the issues:
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update:
Second issue which related with configuration cache solved by removing a single line from gradle.properties
"org.gradle.unsafe.configuration-cache=true"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.