question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Is there any possibility to build the APKs? I do always get strange error messages:

`Could not determine the dependencies of task ‘:wallet:compileAbnDebugJavaWithJavac’.

Could not resolve all task dependencies for configuration ‘:wallet:abnDebugCompileClasspath’. Could not resolve project :sdk. Required by: project :wallet > project :common No matching configuration of project :sdk 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 ‘abn’, attribute ‘org.jetbrains.kotlin.platform.type’ with value ‘androidJvm’ but: - None of the consumable configurations have attributes.`

Keystore and everything is set up properly!

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
dominikponniahcommented, Jun 4, 2021

Thanks @goebelUB ! I tried it firstly using the Debug-Build-Process. Then i opened the full project inside Android-Studio and i was able to build the Apps using a Keystore.

1reaction
goebelUBcommented, Jun 4, 2021

If you are getting the an error along these lines:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':verifier:packageProdRelease'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
   > SigningConfig "release" is missing required property "storePassword".

then the issue is that you haven’t created a keystore, or Gradle doesn’t find all the properties it needs.

Gradle will try to read the keystore-related fields either from your global ~/.gradle/gradle.properties or from the local.properties at the root of the repo. You can configure the keystore file location + password and key alias + password in either of those fields, or pass them as command line arguments to Gradle.


If you don’t want to fight with signing right now, you can build the debug version by replacing Release with Debug:

$ ./gradlew verifier:assembleProdDebug

Note that a) the output path will differ accordingly, and b) you should only to this for testing and use a properly signed build for production.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Building APKs for Android Emulators and devices
Building APKs for Android Emulators and devices. The default file format used when building Android apps with EAS Build is an Android App...
Read more >
Build multiple APKs | Android Developers
Learn how to build and configure your app for multiple APKs.
Read more >
r-- setup.buildAPKs.bash - GitHub
Build Android APKs on device, on your smartphone and tablet with Termux; Make applications for your Android smartphone and tablet! This repository contains ......
Read more >
Building the APK — AndroidAPS 3.0 documentation
Recommended specification of computer for building apk file¶. OS (Only 64 bit), Windows 8 or higher, Mac OS 10.14 or higher, Any Linux...
Read more >
Build and release an Android app - Flutter documentation
When should I build app bundles versus APKs? · What is a fat APK? · What are the supported target architectures? · How...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found