You are currently reviewing an older revision of this page.
Deploying a Component Plug-in fails with the following error printed in the application server log:
2019-06-14 14:10:28,703 [Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Component Plug-in 'com.appian.richtext': Component plug-in approval verification failed. Please contact Appian for approval process
The error includes no stack trace or other information.
This issue can have two underlying causes:
The correct action depends on whether the Component Plug-in is signed or not. To verify if a plug-in is signed, check that the META-INF directory in the plug-in .zip file contains the following files:
META-INF
If all three files are present, the Component Plug-in is signed.
Development and testing of Component Plug-ins requires a registered developer instance. In order to deploy unsigned plug-ins, follow the instructions in the Appian Documentation to register any Appian instances used for development and testing. After successfully completing the registration process, unsigned Component Plug-ins can be deployed on the environment.
Note: Production instances should not be registered under the developer program in order to circumvent signing requirements. Once development is complete, Component Plug-ins should be submitted to Appian for signing so they can be deployed on production instances.
If the error is encountered with a signed Component Plug-in downloaded from the Appian AppMarket, the likely cause of the issue is corruption of the file during the process of downloading or deploying the plug-in. Actions such as e-mailing, FTP transfers and otherwise copying files may introduce unintended changes into a file. To verify whether the file was modified, the MD5 checksums of the files can be compared using the following command.
Windows
certutil -hashfile "<FULL_PATH_TO_PLUGIN_ZIP>" MD5
Linux/Mac
md5sum "<FULL_PATH_TO_PLUGIN_ZIP>"
Both commands will output a 128-bit hash checksum of the file, such as 93dfaf7e0e08fe41f88dda2aee4c6ab9. To verify if changes occurred to the plug-in file, do the following:
93dfaf7e0e08fe41f88dda2aee4c6ab9
<APPIAN_HOME>/_admin/plugins
If the two hashes do not match exactly, the file was modified during download or transfer. In this case, do the following:
If the checksums match, and the error persists, please submit a new Support Case to Appian Technical Support with the plug-in .zip file attached, as well as the link to the plugin in the Appian AppMarket.
This article applies to Appian 19.1 and later.