-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flutter application getting error after adding apptics_flutter package to the project. #5
Comments
@khan-raptee - Thanks for contacting Apptics support! Updating the JAVA version to 17 and Kotlin to 1.8.0 will resolve this issue. Do let me know if you need any further assistance from our end. |
I have updated kotlin to 1.8.0 I have already JAVA 20 below you can check
My android/build.gradle file >> buildscript {
ext.kotlin_version = '1.8.0'
repositories {
google()
mavenCentral()
maven {
url uri('libs')
}
maven {
url "https://maven.zohodl.com/"
}
}
dependencies {
classpath "com.zoho.apptics:apptics-plugin:0.1.2"
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}
}
Still i am getting the same issue >>
C:\Users\zoho_apptics_temp>flutter run
Launching lib\main.dart on 22081283G in debug mode...
1111
{"result":"success"}
com.android.tools.r8.internal.Hc: Sealed classes are not supported as program classes
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:mergeExtDexDebug'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Failed to transform apptics-core-0.2.5.aar (com.zoho.apptics:apptics-core:0.2.5) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=23, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.
> Execution failed for DexingWithClasspathTransform: C:\jetified-apptics-core-0.2.5-runtime.jar.
> Error while dexing.
* 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 25s
Running Gradle task 'assembleDebug'... 87.0s
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
│ To disable the shrinker, pass the `--no-shrink` flag to this command. │
│ To learn more, see: https://developer.android.com/studio/build/shrink-code │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode. │
│ [!] The shrinker may have failed to optimize the Java bytecode. │
│ To disable the shrinker, pass the `--no-shrink` flag to this command. │
│ To disable the shrinker, pass the `--no-shrink` flag to this command. │
│ To learn more, see: https://developer.android.com/studio/build/shrink-code │
│ To learn more, see: https://developer.android.com/studio/build/shrink-code │
└────────────────────────────────────────────────────────────────────────────┘
└────────────────────────────────────────────────────────────────────────────┘
Error: Gradle task assembleDebug failed with exit code 1
Error: Gradle task assembleDebug failed with exit code 1
C:\Users\Kashaf\Desktop\zoho_apptics_temp> |
@khan-raptee - I will share a sample project. Also would request you to please remove the logs as it is exposing some identifiers. |
Thanks. Please share the project
but sometimes in log section we get error to get version 0.2.5
|
flutter-sdk-sample.zip
Also, for the above, it is intended behavior |
>flutter run
Launching lib\main.dart on 22081283G in debug mode...
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':flutter_contacts:compileDebugKotlin'.
> 'compileDebugJavaWithJavac' task (current target is 1.8) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.
Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain
* 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 43s
Running Gradle task 'assembleDebug'... 105.6s
Error: Gradle task assembleDebug failed with exit code 1
|
I am using zoho apptics for flutter my application. I have configured the android plugin and if i run the app it is working fine.To use zoho apptics from my flutter app i should add apptics_flutter package. But when i add the apptics_flutter to my project it starts crashing. Below i have attached the images of how my app works before adding package and after adding the package. please provide solution for this.


The text was updated successfully, but these errors were encountered: