Peter Farlow

@alhazmy13 you haven't released a new version of this library in over 2 years. Can you either release a new version or just mark this repository as read only if...

@aadityapaliwal94 this will not work if your app targets Android 11: "After you update your app to target Android 11 (API level 30), the system ignores the requestLegacyExternalStorage attribute when...

My project uses mockk, and using an x86_64 emulator (API 28+) also solved the problem for me, too https://github.com/mockk/mockk/issues/466#issuecomment-743264258 mockK 1.10.0 and mockK Android 1.9.3 with objenesis forced at 2.6....

Follow up: I also tried removing mockk as an android test dependency and removed all tests that used it. Once I did that, I found that I could once again...

> I agree with @NitroG42 . > > I have migrated the few UI tests I had written to on a new mobile app project **Mockito** believing it would be...

Apologies, I should have commented in the mockk repository. Here's the corresponding issue https://github.com/mockk/mockk/issues/466

Switching to x86_64 emulator in Android Studio solved this for me, too! I am not sure if you can specify the type of emulator architecture in Firebase Test Lab, unfortunately....

Not sure if this helps the mockk team, but I'm seeing this in my logcat logs when tests fail to run on a non x86-64 emulator: ``` 2020-12-16 18:55:46.423 com.my.package.dev....

> **Does anyone have any information on if/when Firebase Test Lab will provide an emulator that uses x86_64?** I created [this StackOverflow question](https://stackoverflow.com/questions/66228193/how-can-i-specify-the-abi-of-my-emulator-to-x86-64-when-using-firebase-test-lab/66234545) to ask about it. Somebody mentioned "x86_64...

> First of all, it now seems evident that this issue is no related to MockK nor to Mockito inasmuch both of these libraries rely to the same internal Android...