This App will not be available in future ios versions, the developers of this App need to update it to improve compatibility!! If you have updated the latest ios system recently, a popup box will pop up when you open the app using signature, or a popup window that is not connected to the Internet will pop up when you describe the file verification certificate.

Starting with ios14.2beta2, the ios signature system will use the latest code signature format

Please update the old App code signature when the new version arrives to avoid iOS warning.

Starting with iOS 14.2 Beta 2, iOS will examine new, more secure signature formats. APP users who start signing in the old format are warned that all apps must be re-signed in the new format. In a future version, the new format will become mandatory and the system will shut down apps that use the old signature format.

Before distributing the APP, sign the application code. Signing proves that you are the creator of the APP and enables the system to detect harmful changes (whether unintentional or malicious) that have occurred since you signed the APP. For security reasons, iOS refuses to launch apps with missing or invalid signatures.

Take a look at your current signature format and check

This change will not affect most applications. For apps distributed through the App Store or TestFlight, App Store Connect first validates your signature, then re-signs the App with an Apple identity, and then downloads it. Applications available through these channels already have new signature formats.

For applications distributed by other means (such as super signatures or enterprise signatures), Xcode and the CoDesign utility have been creating signatures using this new format for several years. If you signed your APP on a Mac running macOS 10.14 or later, the APP already has the new signature format.

To check if the called APP has a new signature, use the utility: myapp.appcoDesign

% codesign -dv /path/to/MyApp.app

Look for similar strings in the output. For any value less than that, you need to re-sign your application. CodeDirectory v=20500v20400

The solution

Please replace your application signature format

If your application does not have a new signature, you will need to re-sign it on a Mac running macOS 10.14 or later. For example, use the following command to re-sign the application package with the signature identity called your Codesign Identity stored in the keystring: % coDesign -s “Your codesign Identity” -f –preserve-metadata /path/to/ myapp.app

If your application contains nested code (such as application extensions, frameworks, or bundled watchOS applications), sign each project individually, starting at the deepest nesting point, to resolve the problem. You can redistribute the application using Xcode running on macOS 10.14 or later.