Based on my device lab where tested on Android Virtual Device API v16 – v29, use GAPPs or not.
The main goal is to quickly give a affirmative detail to BE team, when any error occurred.
Fast way for bug spot inspections at production app. Occurred at BE side?, network call, FE logic, or else.
#Installing CA Cert to android system | |
1. get cert file | |
cd ~/.mitmproxy | |
2. get cert hash | |
// convert cer to pem | |
openssl x509 -inform der -in certificate.cer -out certificate.pem | |
// cert hash for android | |
openssl x509 -inform PEM -subject_hash_old -in mitmproxy-ca.pem | head -1 | |
3. rename cert to hash with *.0 extension | |
nm=c8750f0d.0 | |
cp mitmproxy-ca.pem $nm | |
4. start AVD in writable-system mode | |
emulator -list-avds | |
emulator @Nexus_5X_API_29_x86 -writable-system | |
adb root | |
adb shell "mount -o remount,rw /" | |
5. push cert file | |
adb push $nm /system/etc/security/cacerts | |
6. change file permission | |
adb shell chmod 664 /system/etc/security/cacerts/$nm | |
7. reboot android system | |
adb reboot | |
8. chenk availability after reboot | |
adb shell ls /system/etc/security/cacerts/$nm |




Top comments (0)