how to set delphi android app's idsig file, why my app can not be installed?

[tomye 5]

This issue has been troubling me for a long time. When developing Android applications with Delphi, a .idsig signature file is automatically generated after compilation. However, on some Android systems, this signature file is rejected. The APK can be installed, but it either fails to run or, after a system reboot, my app disappears. There are many problems like this. I can only delete the .idsig file to proceed with the installation, and in most cases, it works fine. However, occasionally, the app still disappears after the Android system reboots. How should I properly configure this .idsig file?

[bravesofts 24]

Resolving .idsig Issues in Delphi Android Apps

Understand the .idsig File Role

The .idsig file is generated during APK signing with APK Signature Scheme V2/V3.

It ensures APK integrity. Deleting it forces fallback to legacy signing (V1).

Update Your SDK Tools

Use the latest Android SDK and Build Tools compatible with Delphi.

Ensure Android SDK Build Tools 30.0.0 or higher is installed.

Verify SDK paths in Tools > Options > SDK Manager.

Prevent App Disappearance After Reboot

Ensure consistent and trusted APK signing with a proper keystore.

Avoid modifying the APK (e.g., deleting .idsig) after signing.

Test on Multiple Devices

Test your app on various devices and Android versions, focusing on 7.0 and above.

Check for Manufacturer-Specific Issues

Investigate device-specific forums for issues with customized Android versions.

Use Logcat for Debugging

Gather installation/runtime logs using:

adb shell logcat | grep "com.yourCompany.yourAppName"

Share the log file with us here for further analysis.

*Always use at least Android SDK Build Tools 30.0.0 or higher to avoid outdated signing issues.*

[tomye 5]

On 1/17/2025 at 9:16 AM, bravesofts said:

Resolving .idsig Issues in Delphi Android Apps

Understand the .idsig File Role

The .idsig file is generated during APK signing with APK Signature Scheme V2/V3.

It ensures APK integrity. Deleting it forces fallback to legacy signing (V1).

Update Your SDK Tools

Use the latest Android SDK and Build Tools compatible with Delphi.

Ensure Android SDK Build Tools 30.0.0 or higher is installed.

Verify SDK paths in Tools > Options > SDK Manager.

Prevent App Disappearance After Reboot

Ensure consistent and trusted APK signing with a proper keystore.

Avoid modifying the APK (e.g., deleting .idsig) after signing.

Test on Multiple Devices

Test your app on various devices and Android versions, focusing on 7.0 and above.

Check for Manufacturer-Specific Issues

Investigate device-specific forums for issues with customized Android versions.

Use Logcat for Debugging

Gather installation/runtime logs using:

adb shell logcat | grep "com.yourCompany.yourAppName"

Share the log file with us here for further analysis.

*Always use at least Android SDK Build Tools 30.0.0 or higher to avoid outdated signing issues.*

 

thank you , help me a lot 🙂