Bug P2
Status Update
No update yet.
Comments
jo...@google.com
Dnkdmskskjfkfng
no...@google.com
Note that BaseDexClassLoader was added in ICS (API 14):
https://android.googlesource.com/platform/libcore/+/ea52753a0f80fcd70acfe9150ecb854511ff38db
Perhaps we could use "is a descendant of BaseDexClassLoader" for API 14+ but use "is a descendant of DexClassLoader OR PathClassLoader" for API <14.
Perhaps we could use "is a descendant of BaseDexClassLoader" for API 14+ but use "is a descendant of DexClassLoader OR PathClassLoader" for API <14.
br...@google.com
Fix for multidex support has been submitted.
aravinds has a CL open to update the multidex build in piper.
Once that is in we can start to remove the customized Robolectric support for multidex
aravinds has a CL open to update the multidex build in piper.
Once that is in we can start to remove the customized Robolectric support for multidex
su...@bt.com
Unit tests are failing with multidex failed. Is this solution ready. Could you please confirm
java.lang.RuntimeException: MultiDex installation failed (C:\Users\dfd\AppData\Local\Temp\robolectric-Method_testsfdsfdsfdsl\com.x.y-sourceDir (Access is denied)).
java.lang.RuntimeException: MultiDex installation failed (C:\Users\dfd\AppData\Local\Temp\robolectric-Method_testsfdsfdsfdsl\com.x.y-sourceDir (Access is denied)).
ba...@gmail.com
Any update on this issue
jo...@google.com
Robolectric 4.0 includes an androidx.multidex shadow which should fix your issue.
The underlying fix to Multidex (to make it compatible with test modes) has been submitted but we're still in the release process (it has to make its way through an internal release first which is the delay). Once that's happened we can push a public release, at that point you won't need the Robolectric shadow.
The underlying fix to Multidex (to make it compatible with test modes) has been submitted but we're still in the release process (it has to make its way through an internal release first which is the delay). Once that's happened we can push a public release, at that point you won't need the Robolectric shadow.
su...@bt.com
Thank you.That addressed my problem.
as...@gmail.com
Issue:279323712
Description
At some point Robolectric changed so that Context.getClassLoader() would return an actual ClassLoader breaking this check.
To fix this, I suspect the correct check is that the ClassLoader is a decedent of BaseDexClassLoader
Robolectric has worked around this by providing a no-op Shadow of MultiDex but we don't really want to maintain shadows for non-Framework classes. With the androidx namespace changes this would require another shadow.