[criticalAY]

Note

Assisted-by: Claude Opus 5

Purpose / Description

DeckPickerContextMenuTest does not extend RobolectricTest, so it never calls RustBackendLoader.ensureSetup(). It only passes when some test that does happens to run earlier in the same JVM. When it runs first, every one of its tests dies on:

java.lang.UnsatisfiedLinkError: 'byte[][] net.ankiweb.rsdroid.NativeMethods.openBackend(byte[])'
    at net.ankiweb.rsdroid.Backend.<init>(Backend.kt:86)
    at com.ichi2.anki.CollectionManager.getTR(CollectionManager.kt:188)
    at com.ichi2.anki.dialogs.DeckPickerContextMenu$DeckPickerContextMenuOption.label(DeckPickerContextMenu.kt:98)

Fixes

• Part of [Bug] Unit Tests: java.lang.UnsatisfiedLinkError: 'byte[][] net.ankiweb.rsdroid.NativeMethods.openBackend(byte[])' when mixing RunWith(AndroidJUnit4::class) #14796

How Has This Been Tested?

CI and here:

• ./gradlew :AnkiDroid:testPlayDebugUnitTest --tests "com.ichi2.anki.dialogs.DeckPickerContextMenuTest"

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the [Google Accessibility Scanner]

[david-allison]

What do you think about fixing this upstream?

• feat(class-loader): handle backend requests from multiple classloaders Anki-Android-Backend#713

[david-allison]

You can use JvmTest I believe

[criticalAY]

What do you think about fixing this upstream?

Yeah makes more sense. Will review the PR upstream give me few hours

[david-allison]

I'm an "approve" here regardless, if there's a TODO: PERF to move it can be done