You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more useful now we're considering re-architecting the module structure of the app. If we can remove 'Robolectric' from a test suite for a module, we get huge savings. There are many tests which only use Robolectric due to the rsdroid/libanki, but we can't feasibly
Fixes local builds: Direct local .aar file dependencies are not supported when building an AAR.
rsdroid/libanki, but we can't feasiblyDirect local .aar file dependencies are not supported when building an AAR.androidTestInitial thoughts
.sofiles work?rsdroidwith.sofiles for each of the 4 mainstream Android targets.rsdroid-testingwithrsdroid.dll,librsdroid.dylibandlibrsdroid.sofor RobolectricRustBackendLoaderbuild/generated/anki_artifactsAssetManager- mmap onto the apkConstraints
aar->aarreferences are unacceptableapk-> localaaranki_artifactsare heavily latency sensitive: Pages and web content used by the study screen