giuliohome
commented
1 year ago I see I replicated all in my codespaces and my diff is
@giuliohome ➜ /workspaces/mastodon-android (master) $ git diff
diff --git a/build.gradle b/build.gradle
index c61b945e..c4715843 100644
--- a/build.gradle
+++ b/build.gradle
@@ -5,7 +5,7 @@ buildscript {
mavenCentral()
}
dependencies {
- classpath "com.android.tools.build:gradle:7.1.3"
+ classpath "com.android.tools.build:gradle:7.4.2"
classpath "com.google.android.libraries.mapsplatform.secrets-gradle-plugin:secrets-gradle-plugin:2.0.1"
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
diff --git a/gradle/wrapper/gradle-wrapper.properties b/gradle/wrapper/gradle-wrapper.properties
index 464f9805..4c4f8616 100644
--- a/gradle/wrapper/gradle-wrapper.properties
+++ b/gradle/wrapper/gradle-wrapper.properties
@@ -1,6 +1,6 @@
#Thu Jan 13 11:33:43 MSK 2022
distributionBase=GRADLE_USER_HOME
-distributionUrl=https\://services.gradle.org/distributions/gradle-7.3.3-bin.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-bin.zip
distributionPath=wrapper/dists
zipStorePath=wrapper/dists
zipStoreBase=GRADLE_USER_HOMEand I guess I have to add --no-daemon for codespaces
@giuliohome ➜ /workspaces/mastodon-android (master) $ ./gradlew connectedAndroidTest --no-daemon
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.6/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
[adb]: * daemon not running; starting now at tcp:5037
[adb]: * daemon started successfully
> Task :mastodon:connectedDebugAndroidTest FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':mastodon:connectedDebugAndroidTest'.
> com.android.builder.testing.api.DeviceException: No connected devices!
* 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 2s
56 actionable tasks: 9 executed, 47 up-to-dateand No connected devices! is reasonable in codespaces 😄
I'll try again later on my actual linux laptop only from the shell with ./gradlew connectedAndroidTest, without starting the instrumented tests from android studio, momentarily... But I'd like to know how to run these tests also from Android Studio, if possible.
grishka
Thank you for the awesome work. Tried building with Android Studio and the apk was ok (even though I used latest AS and jdk and a fake signature). I only changed the jdk from AS as per your suggestion in another issue and I upgraded the gradle plugin.
My question about the tests because I couldn't run them at first trial: are you using Espresso tests, can them be built and executed from Android Studio, should I tweak anything in gradle settings to make them work?
Thank you again