Zip cannot be parsed after being converted into apk. At present, many people still use Android phones. When installing software, Android phones need to parse the apk installation package. When installing apk files, we sometimes encounter situations that cannot be parsed. Let's take a look at the situation that zip can't be parsed after being converted into apk.
1 cannot be parsed after zip is converted to apk. Step 1: Get apk programs through regular channels and well-known websites. The place where I strongly recommend downloading software here is the mobile phone Android market. The software on this website was released after strict testing. After downloading to the mobile phone, it can generally be installed and run well, and most of the software can be used for free, without malicious plug-ins.
Step 2: apk versions are incompatible. In general, when the version of the apk program downloaded from the Internet is higher than the current version of the mobile phone, the warning "Error in parsing the package" will appear when installing the program. The solution to this situation is: for this apk program, search for similar applications in the Android market, but the version should not be higher than the current mobile phone version to download, install and function.
Step 3: The apk plan is incomplete. Some mobile phones have download tools that don't have breakpoint resume function, so the downloaded programs may be downloaded incompletely, and some programs may be lost first. For this kind of problem, it is suggested to download it again, or download it through a computer, and then copy the apk program to the mobile phone memory card with the help of the data cable before installation.
Step 4: The current mobile phone does not support Chinese names or paths, and does not support long file names. The solution is to rename the file, and the name only contains English letters (but note that the suffix ".apk" should be kept), such as renaming it to "abc.apk", and then move the installer after the change is completed.
Step 5: The apk program can't be installed normally due to insufficient memory of the mobile phone, poor contact of the mobile phone memory card and poor quality of the memory card. In view of this kind of problem, try to plug in the mobile phone to expand the memory card as much as possible. If it doesn't work, replace it with a high-quality memory card (there are parallel memory cards on the market now, so be careful when buying them. Generally speaking, the nominal capacity of parallel memory card is greater than its realized capacity).
If the mobile phone uses parallel imports or poor quality memory cards, even if the data stored in the memory card is larger than the actual memory capacity, the program will not report an error, but the data has already been lost. In this case, the installation of apk program is definitely unsuccessful.
Step 6: The specified file path does not exist or the wrong path is specified. A typical case is that it has been published on the Internet that the program cannot be installed due to improper settings of RE Manager. The solution is: enter RE Manager and click Settings > One-click Settings->; "Home folder option", if set to "sdcard", an error message "There is something wrong with the analysis package" will appear, but if set to "",the installation can be successful. I suggest you try!
Step 7: The APK installer may be incompatible or not installed. This usually happens in mobile phones with ROM. After the mobile phone was refreshed, some necessary software such as "Hulk" and "Install" was not installed due to the need of simplification, resulting in abnormal installation of apk program. The solution is to download the relevant apk installer from the Android market, and then install the apk application through the apk installer.
Step 8: The mobile phone may be poisoned. Download 36 mobile phones from the Android market. Security guards kill mobile phone viruses to ensure that mobile phones are in the best safe operation state.
Unable to parse after converting zip to apk. 2. Summary of abnormal analysis package when installing apk.
1.apk was damaged during downloading.
This kind of situation that can be said without too much expansion is rare. The apk file was destroyed during the network download process, resulting in an exception in the parsing package.
2. There is a problem with installing apk code.
AppUtils.installApp () is recommended here. Methods apk was installed, which was compatible with Android8.0 version 8.0, including permission application for installing third-party applications.
Don't forget to declare this permission in the manifest file before dynamic application.
3. The download of apk by the high version was unsuccessful.
This problem is a problem I have encountered in eliminating apk at present. In the previous project, the files were downloaded in the download folder. However, after Android 10, the storage permissions have changed, which leads to the failure to download files directly to the download folder, resulting in the failure of file download and the exception of parsing packages.
The solution is only to adapt to the path problem after Android 10.
It is recommended to download in the files folder of the app itself, which can solve the problem. Just use this path Pathutils. getExternalAppDownloadpath()。
4. Permission not applied
There are two permissions to be mentioned here, one is the storage permission, and the other is the permission to install third-party applications.
To store permissions, Android6.0 needs to be applied manually, so I won't go into details here.
5.apk signature problem
This is also a common problem, because my project is reinforced with 360, and then re-signed.
I have been re-signing with the command line before, and I didn't pay much attention. In fact, the parameters of v2 need to be declared, and the reinforcement installation package has never been signed by v2.
However, Android7.0 version 7.0 needs to verify the v2 version signature, which is naturally a problem.
Then I gave it a try and packaged a signature tool without having to enter commands every time.
Interested parties can see this link as Tool:apk signature verification cracking tool Apk signature cracking tool.
There is something wrong with the installation of 6.6. Android 12 version.
The application with the targetSdkVersion of 3 1 and the target of Android 12 must use v2 signature, and the activities, services and broadcast receivers used must contain intent-filter, and the display declares the android:exported attribute.
In the AndroidManifest file, there are four components with intent-filter attribute, so it is necessary to declare the exported attribute as true.
If the system is adapted to Android 12, the sdk called is 3 1. It may need to be adjusted.
The installation failed 22, probably because the android:exported="false "field was not added to the activity or recipient and service.
Note that android:exported must be set to true in launcheractivity. This means external reference.
If it is not set to true in launcheractivity. Then clicking the application icon will cause the application not to be installed.
If the installation fails-127. Because the permissions declared in the list are duplicate.
Unable to parse 3 apk after converting zip to apk. What if the installation fails?
1. The remaining storage space of the mobile phone system is insufficient, resulting in the installation failure:
Prompt situation:
A. The prompt is "ADB _ install _ failed _ insurance _ storage", indicating that the storage space of the mobile phone is insufficient;
B. The prompt is "ADB_INSTALL_FAILED_DEXOPT", which means that the storage space of the mobile phone is insufficient, resulting in the failure of APK decoding;
C. The prompt is "ADB _ install _ failed _ device _ no space", which means that the copy of apk failed due to insufficient storage space of the mobile phone;
D. The prompt is "ADB _ install _ failed _ device _ copy _ failed", indicating that the file copy failed;
Solution:
Please try to uninstall unnecessary applications/games to free up more space on your phone.
Or move some applications stored in the phone memory (not all applications can be moved) to the SD card, or free up some space.
2. The connection between the mobile phone and the computer failed, resulting in the installation failure:
Prompt situation:
A. The prompt is "ADB_INSTALL_DEVICES_NOT_FOUND", indicating that the device cannot be found;
B the prompt is "ADB _ install _ failed _ device _ offline", indicating that the equipment is offline;
Solution:
Please plug and unplug the USB cable again, or replace the USB socket, and try to connect the phone successfully before trying to install APK.
3. You need to try to uninstall APK and reinstall it to solve the problem of failed installation:
Prompt situation:
A. The prompt is "ADB _ install _ failed _ update _ inconsistent", indicating that the update is incomplete. Please uninstall again and try again.
B. The prompt is "ADB _ install _ failed _ conflicting _ provider", which indicates that the conflict between software vendors and mobile phones may not be resolved;
C prompt is "ADB _ Install _ Analyze _ Failed _ Inconsible _ Certificates", indicating that the document authentication is inconsistent;
D the prompt is "ADB _ install _ failed _ already _ exists", indicating that the target already exists;
E prompt is "ADB _ install _ failed _ invalid _ zip _ file", which means illegal zip file;
Solution:
Please try to uninstall APK (if it is available on the original phone), download APK again and install it.
4. Need to refresh the mobile phone Android system to solve the installation failure problem:
Prompt situation:
A. The prompt is "ADB_INSTALL_FAILED_OLDER_SDK", indicating that the version of your mobile phone system is lower than the required version of the software;
Solution:
Please try to refresh the mobile phone Android system to solve the problem of installation failure.
Friendly reminder: Brush machine is risky, so you need to operate it carefully or with the help of experienced friends.
5. Installation failed due to software installation authorization:
Prompt situation:
A. The prompt is "ADB _ install _ parse _ failed _ no _ certificates", indicating that the file authentication failed;
Solution:
Please go to System Settings-Applications-(Installation and Debugging)-Check Unknown Sources/Unknown Sources (allowing the installation of applications in the unofficial Android market).
6. Installation failed due to "container error":
Prompt situation:
A. The prompt is "ADB _ install _ failed _ container _ error", which indicates a container error, and generally appears when installing apk to sdcard; ;
Solution:
Step 1: Connect G7 to the computer with data cable, and adjust the connection mode to "disk drive" mode;
Step 2: Use the computer's resource manager to enter. Android_secure directory under SD card (the resource manager on the mobile phone can't see this file);
Step 3: Find the file "smdl2tmp 1.asec" and delete it (you can cut it first if you are worried). (Note that the fourth letter of the file name is lowercase l, not the number 1).