Android: Building app fails using Java version > 8

[astroanax]

I really appreciate your efforts in creating such a useful application. I am running into the following error while building on Arch Linux.

> Task :presentation:compileLicenseDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.5.1/userguide/command_line_interface.html#sec:command_line_warnings
121 actionable tasks: 1 executed, 120 up-to-date
error: error while generating class <anonymous org.cryptomator.presentation.workflow.AddExistingVaultWorkflow$1>
  (illegal signature attribute for type CAP#1)
  where CAP#1 is a fresh type-variable:
    CAP#1 extends View from capture of ?
Note: /home/phantom/dev/tools/cryptomator-android/presentation/src/main/java/org/cryptomator/presentation/util/PasswordStrengthUtil.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':presentation:compileLicenseDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 9s

The complete log (./gradlew assembleLicenseDebug | tee logs.txt): https://gist.github.com/Phantom-Rehan/c9d716f0b6ac1304e3cd789f5177256d

My secrets.properties looks like this, literally:

ONEDRIVE_API_KEY=abcdef
DROPBOX_API_KEY=abcdef
DROPBOX_API_KEY_DB=abcdef

Useful Information:

 phantom@elysium 130 ~/dev/tools/cryptomator-android develop !1 ?1
> java --version
openjdk 14.0.2 2020-07-14
OpenJDK Runtime Environment (build 14.0.2+12)
OpenJDK 64-Bit Server VM (build 14.0.2+12, mixed mode)

Btw, is releasing the app on github releases and or f-droid planned? Again, appreciate your efforts.

[overheadhunter]

Btw, is releasing the app on github releases and or f-droid planned?

Can't help you with the technical details on Gradle, but at least I can answer this question: Yes publishing the APK on F-Droid is planned and GH Releases is a great idea, too.

[scollovati]

Btw, is releasing the app on github releases and or f-droid planned?

Can't help you with the technical details on Gradle, but at least I can answer this question: Yes publishing the APK on F-Droid is planned and GH Releases is a great idea, too.

+1 for the F-Droid Release plan. I wanted to comment here https://github.com/cryptomator/android/issues/1 but it was closed.

[SailReal]

@Phantom-Rehan as mentioned in the Readme, please use Java 8.

Related to F-Droid, just reopened #1

[astroanax]

> java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)

Hmm, some other error this time:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':data:compileLicenseDebugAidl'.
> Could not resolve all task dependencies for configuration ':data:licenseDebugCompileClasspath'.
   > Could not resolve project :msa-auth-for-android.
     Required by:
         project :data
      > No matching configuration of project :msa-auth-for-android was found. The consumer was configured to find an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'version' with value 'license', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - None of the consumable configurations have attributes.

I did a gradlew clean, but that seemed to give errors, so I cloned the repo again.
Log: https://gist.github.com/Phantom-Rehan/41f97fad5be77c5ca31a21786233dfee
I would still have to purchase a license to use the app after building it, right?

[SailReal]

Again as mentioned in the Readme, use the --recurse-submodules parameter while cloning the repo to also initialize the submodules or use git submodule init && git submodule update to archive the same result when already cloned.

[astroanax]

I am really sorry, I should have read the README carefully. Now the build is successful, without any errors.