Magisk/app/test/proguard-rules.pro

# Keep all test dependencies
-keep class org.junit.** { *; }
-keep class androidx.test.** { *; }

# Make sure the classloader constructor is kept
-keepclassmembers class com.topjohnwu.magisk.test.TestClassLoader { <init>(); }

# Repackage dependencies
-repackageclasses 'deps'
-allowaccessmodification

# Keep attributes for stacktrace
-keepattributes *
Redesign test APK architecture The test APK and the main APK share the same process and classloader, and in the non-hidden case, the test APK's classes take precedence over the ones in the main APK. This causes issues because the test APK and main APK share some dependencies, but don't always use the same version. This is especially problematic for the Kotlin stdlib and AndroidX dependencies. The solution here is to rely on R8's obfuscation feature and repackage all potentially conflicting classes into a separate package in the test APK. To ensure that the test classes are always using the same classes as the main APK, we have to directly implement all tests inside the main APK, making the test APK purely a "test runner with test dependencies". As a result, the test APK can only be used when built in release mode, because R8 no longer allow class obfuscation to be enabled when building for debug versions. 2024-12-25 20:17:57 -08:00			`# Keep all test dependencies`
			`-keep class org.junit.** { *; }`
			`-keep class androidx.test.** { *; }`

			`# Make sure the classloader constructor is kept`
			`-keepclassmembers class com.topjohnwu.magisk.test.TestClassLoader { <init>(); }`

			`# Repackage dependencies`
			`-repackageclasses 'deps'`
			`-allowaccessmodification`

			`# Keep attributes for stacktrace`
			`-keepattributes *`