I've made a phone app with that tech (https://apkpure.com/donemychores/com.dienique.housechores.android), but what I'm looking for is an up-to-date way of writing android apps with scala.
There are some efforts for supporting scala 2.12 and sbt 1.0,you can find those experimental branch in github
finally have some break from work
I'm trying to use the current version of mapbox-android-sdk (9.1.0) with sbt-android. It has com.facebook.soloader as a transitive dependency and now I get this error when compiling:
The error disappears when I exclude
Does anybody have an idea by what this could be caused and how it could be fixed?
[error] (guidemate/android:rGenerator) Error: more than one library with package name 'com.facebook.soloader'The error disappears when I exclude
com.facebook.soloader (as expected), but this library is probably needed somewhere, so I don't know if this is really an option.Does anybody have an idea by what this could be caused and how it could be fixed?
I am starting sbt in project root directory.
@pfn Concerning the problem
more than one library with package name ...: It seems to have been a problem in gradle, too. Here, it is suggested that the problem was fixed in a newer gradle version: https://stackoverflow.com/questions/51024717/error-more-than-one-library-with-package-name-android-support-graphics-drawabl
as for value, since android is stuck with scala 2.11 at best, I don't really feel it's worthwhile to keep sbt-android up to date anymore
the fix is to use only the correct dependency graph
it's not a plugin fix to resolve this
You are right, the problem that we are stuck with scala 2.11 is really annoying. I would not start a new Android project with Scala either. It is really a problem that it is not officially supported.
However, I still have an Android project that uses Scala, so it would be great if it could at least still be built somehow in the near future.
At the moment, it is ok just not to use the support library version 28 oder higher. I just cannot update the dependencies any further then.
However, I still have an Android project that uses Scala, so it would be great if it could at least still be built somehow in the near future.
At the moment, it is ok just not to use the support library version 28 oder higher. I just cannot update the dependencies any further then.
Maybe it would be best to migrate the whole code to Kotlin
hey there, I have been fighting with a weird issue when running processManifest, it seems to complain about a tools:targetApi field coming from one of my dependency, here's the start of the stack trace:
java.lang.RuntimeException: [/home/regb/.android/sbt/exploded-aars/com.google.firebase-firebase-common-19.3.0] /home/regb/.android/sbt/exploded-aars/com.google.firebase-firebase-common-19.3.0/AndroidManifest.xml:32:9-36:35: Error: Invalid instruction 'targetApi', valid instructions are : REMOVE,REPLACE,STRICT
I haven't been able to figure out exactly what it the reason for that, I suspect maybe this is a new feature of the manifest parser and sbt-android might not have this feature? I've tried to read through the code of sbt-android and it seems like it links against the manifmerger library from Android, which would be consistent with the theory if it links against a too-old version?
Any solution to this?
It happened after I bumped a bunch of firebase versions ahead, so I will try to go back in time until I can figure it out, but is there something else that I can do?
java.lang.RuntimeException: [/home/regb/.android/sbt/exploded-aars/com.google.firebase-firebase-common-19.3.0] /home/regb/.android/sbt/exploded-aars/com.google.firebase-firebase-common-19.3.0/AndroidManifest.xml:32:9-36:35: Error: Invalid instruction 'targetApi', valid instructions are : REMOVE,REPLACE,STRICT
I haven't been able to figure out exactly what it the reason for that, I suspect maybe this is a new feature of the manifest parser and sbt-android might not have this feature? I've tried to read through the code of sbt-android and it seems like it links against the manifmerger library from Android, which would be consistent with the theory if it links against a too-old version?
Any solution to this?
It happened after I bumped a bunch of firebase versions ahead, so I will try to go back in time until I can figure it out, but is there something else that I can do?
Alright so I was able to confirm this, firebase-common in version 19.3.0 has this additional attribute:
tools:targetApi="n"
which is not present in version 19.0.0, and when I override which version to use all seems fine?
Is there some settings somewhere that I can tune to enable the support for tools:targetApi ?
By skimming through the messages above, I think I understand that there's not much motivation left to maintain sbt-android up to date (maybe due to the fact that both Scala and Android liked to ignore each other?). but I just wanted to say that I personally find this plugin incredibly useful, I have been developing a few native Android games with Scala, using this plugin, and I have also been working on a large cross-platform game library for Scala (same scala code, multiple backend: scalajs, scalanative, awt, android), and in this project, the sbt-android plugin is critical to support the Android backend.
So thanks for all the hard work anyway!
So thanks for all the hard work anyway!
I haven't checked to see if desugar works any better, but I don't think so
I don't actually know much about the internals, and haven't looked too much into the Android/java8/scala 2.12 compatibility, but wouldn't it be possible to use d8 to convert the scala bytecode to something compatible for Android? https://developer.android.com/studio/command-line/d8
at least not when I last tried it 2 years ago
I need a technician to crack Android software
i Can pay
scala 2.11 works without any problems with android 10
