Let's start with a bug that was cheated by the app store

I'm doing it today APP When automated testing , On a whim Case The development machine of has been switched to red rice  9A This machine . Then I started to look for BUG Cause of the day .

BUG describe

A new version of the product has been released recently , Most responsible for automated testing , Start developing test cases for this new version of the feature , Because another device is busy running regression test automation , So I took out this red rice mobile phone . Connect the data cable , open CMD, Enter the following command , Check whether the link is normal .

adb devices

Everything is ready. , open IDEA, Start writing use case code for automated testing , Soon , You have completed the writing of a use case . Come on , Let's run it and see .

Oh dear , Why did you make a mistake , It was normal just now , The environment has not been modified , Just changed a cell phone , Why not .

To pass by by hand adb Command installation to see .

adb install xxxxxxxx.apk

It can't be installed , Try another version

Why ？ The old version is OK , It's not that the mobile phone is broken . Go and find out what this error number means

INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113

The reason is that some applications use native libraries （NDK,Native Lib）, These libraries are usually compiled to arm Architecturally cpu, stay x86 Such errors will be reported when running on .

Blind guessing is when the developer modifies the compilation configuration when compiling the code , But this file will not be modified for no reason , This is not to find something for yourself ？

Problem location

Just think I put BUG When the tickets were written, I saw a notice like this .

So I searched the Internet , The app stores of other Huawei manufacturers have similar regulations . What a coincidence , The developer has modified the configuration of this section in this version , Changed to pure 64 Bit compilation

That is to say, from the previous

android {
 defaultConfig { 
 ndk{
 //  It's packaged  APK  The document command contains  ARM  Dynamic library of instruction set
 abiFilters "armeabi-v7a", "arm64-v8a", "x86", "x86_64"
 }
 }
}


Changed to

android {
 defaultConfig { 
 ndk{
 //  It's packaged  APK  The document command contains  ARM  Dynamic library of instruction set
 abiFilters "x86_64"
 }
 }
}


What is the configuration of my mobile phone ？ adopt ADB Check it out.

adb shell getprop ro.product.cpu.abi

That's why ！

Then I checked , Of this mobile phone CPU Related content , Usually I don't go to a certain degree to check technical articles , But there are still many such articles .

To make a long story short , Even if my mobile phone leaves the stage of automatic development in the future , Maybe it can also be used to test small programs , Not good either. ！ Don't wechat have to be upgraded ！

If today's article helps you , Welcome to forward it to your friends .

I am a Tango, An ape who loves sharing technology , See you next time .