0.7.0 in studio 3.5 w JRE 1.8 #232
Comments
|
@johnda98 what is your |
|
|
Thanks Abonander :-) quick action.. you rock! Ans is 15. as below. also far below is the top level gradle .build apply plugin: 'com.android.application' android { dependencies { } / Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript { } allprojects { } task clean(type: Delete) { |
|
Yes, your |
DApp was compiling fine.. just insertered the .7.0 SDK implementation and yes then the compiler threw .. so you reference the Key as it is what it is in the .7.0 HH SDK release. Hey I did notice in the HH intellij docs for Devs to put "Note: sourceCompatibility should be set to 11".. where in my proj structure config ? and or put that in one of the build.gradles' |
oh ok.. I'll try that now and re-build |
|
thats the reality then .. that a DApp on mobile would be that then that can handle the hedera classes etc.. -27% of the droid market |
|
You do not need Java 11 anymore, no. We do use some Java 8 features, so JDK 1.8 is the minimum which you have. |
|
We can fix it so you don't have to set |
thats cool.. its bloody edge.. so -27% is fine for our MvP.. PoC in USA terms :-) I re build and it seems ok now.. Nexus 5 API24 popped up fine :-)) |
|
We can close this issue then... anything else I should be aware of ? save me raising any other daft questions ;) :-) |
Oh i got this also "Invoke-customs are only supported starting with Android O (--min-api 26) |
|
MethodHandle.invoke and MethodHandle.invokeExact are only supported starting with Android O (--min-api 26) |
|
We haven't tested the SDK extensively on Android yet; before we fixed it to be compatible with Java 8 we had a really hacky solution to make things work but we haven't tried it since then.
Does it say what code is triggering that error? Otherwise I'm going to be spending a long time looking for it. |
ok.. let me clean and rebuild.. will paste the stack trace ASAP in a min |
|
as below.. the unexpanded trace.. org.gradle.internal.exceptions.LocationAwareException: Execution failed for task ':app:mergeDebugJavaResource'. |
|
Here is the other dump from 'Run tasks' in build output org.gradle.execution.MultipleBuildFailures: Build completed with 1 failures. |
|
I'm on ubuntu 16.04 server.. stable and my eclipse w hedera works dandy on it :-) |
|
The emulator is up with the basic App .. "Invoke-customs are only supported starting with Android O (--min-api 26)" |
|
Yes sir.. sadly by |
|
I did some investigating and you need to do a couple more things to get it working as-is:
(You can probably remove some of those lines and it'll still build, that's just the solution I found here: https://stackoverflow.com/a/47509465) |
|
a bit obvious.. compile options and try to pull in the dex_file. will advise e: Bad encoded_array value: Failure to verify dex file '/data/app/com.leveridgesystems.johnsap |
|
Ok looks good.. thanks team. can close this config help issue. |
|
Thanks HH Eng.. for the config help... all set. |
Was kindly informed .7.0 would be ok with java 8 on studio.. included repo dependency and ran the app - compiler complained "Static interface methods are only supported starting with Android N (--min-api 24): com.hedera.hashgraph.sdk.crypto.Key com.hedera.hashgraph.sdk.crypto.Key.fromProtoKey(com.hederahashgraph.api.proto.java.Key)"
probably something simple.. thanks Mehcode for any kind navigation offered on this.
dont really want to switch to Kotlin if its fairly easy to dev with HH java sdk compatible with droid sdk
The text was updated successfully, but these errors were encountered: