Native Integrations : App can not be installed on the terminal

For ISVs, there are 2 ways to distribute their app on a terminal :

Upload it to the PAX Store developer center. From there, the app is signed automatically by PAX and distributed to the terminals using a mechanism built by PAX. If the ISV goes this route the app will almost always be installed successfully. It is not possible to make a mistake signing the APK (android app) or other.
Manually install the app via cable on the terminal using Android ADB commands. This is not the preferred route but some ISVs prefer pushing their apps manually on the terminal. This is when there is room for mistakes and there might be issues for an ISV to install their app on the terminal :
1. Each new version of their app needs to be signed by Handpoint to be installed on the terminal, this is a manual process and if the ISV forgets to ask Handpoint to sign a new version of their application it will not be installed correctly on the terminal.

There are a few other reasons why the android system might not install the app:

Insufficient Storage.
Corrupted/Contaminated App File.
Storage Location.
SD Card Not Mounted in the Device.
Corrupted Storage.
Application Permission.

(https://www.imobie.com/support/android-app-not-installed.htm )

For the ISV to be able to troubleshoot the exact reason why their app can not be installed, it would be important to get the logs of the terminal from the PAX Store and send them to the ISV so they can troubleshoot further. In most cases the reason why the app is not installed would appear in the logs (https://handpoint.atlassian.net/wiki/spaces/PD/pages/3858333726)