| Age | Commit message (Collapse) | Author |
|---|
|
The dex number is considered invalid if it is not found in
SharedPreferences or the persisted value is less than 1. My only theory
for how this could occur is SharedPreferences corruption.
In this scenario prior to this change, MultiDex would think there were
no secondary dex files to extract and the application would crash at
runtime with ClassNotFoundException.
Bug: 62483082
Change-Id: If3671b53b06bb2fb97a9dd82858a6f43b0e1dc1c
Test: mmma -j frameworks/multidex
|
|
This saves 5-10ms on a JellyBean Samsung Nexus S for the check
to see whether the VM supports multidex natively.
On a newer Samsung S7 phone it saves 0.5 ms.
Test: manually tested on old and new devices.
Bug: 74259172
Change-Id: Ic05645deb5b4b990d07c726aa0fdd5f0cfa5884b
|
|
Robolectric at somepoint changed to return a valid Java ClassLoader from
Context.getClassLoader(), breaking the check in MultiDex.
Modify this check to ensure a valid Dex compatible classloader.
Test: Added integration tests in Robolectric; m -j checkbuild
Change-Id: I9df517e25460daa5fabfe8cba88cdc5d9bb16de2
|
|
Bug: 74397601
Test: make
Change-Id: Iddea6f92cc7796125cf4d1ba86cf9b7425daef72
|
