Hello appian developers:
I am developing a connected system type plugin and although the plugin has been validated by Appian, when I proceed to deploy it to Appian Cloud, this deployment fails with the following error:
2025-08-07 06:57:09,799 [http-nio-8080-exec-21839] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to enable Plug-in 'Instagram Connected System' (InstagramConnectedSystem) version 1.1.0: 'There was a problem loading the module descriptor: com.appiancorp.connectedsystems.templateframework.osgi.ConnectedSystemTemplateModule.<br/>com.nttdata.appian.plugins.SocialConnectedSystem.InstagramConnectedSystemTemplate is not of type com.appian.connectedsystems.templateframework.sdk.ConnectedSystemTemplate'2025-08-07 06:57:09,800 [http-nio-8080-exec-21839] ERROR com.appiancorp.plugins.DeployUploadedPluginReaction - Failed to deploy plugin file socialConnectedSystem.jarjava.lang.IllegalStateException: Plugin was deployed but not successfully enabledat com.appiancorp.plugins.DeployPluginService.lambda$installPlugin$2(DeployPluginService.java:134)
It seems to be a problem in the class that defines the Connected system, but I'm not sure if it means that the class must be of the type indicated in the error com.appian.connectedsystems.templateframework.sdk.ConnectedSystemTemplate, which doesn't match the examples provided by appian in its documentation, which indicates the use of the com.appian.connectedsystems.simplified.sdk.SimpleConnectedSystemTemplate class, or that the type indicated in the error is not correctly implemented by the plugin. The connected system I am developing extends the com.appian.connectedsystems.simplified.sdk.oauth.SimpleOAuthConnectedSystemTemplate class which in turn extends the aforementioned com.appian.connectedsystems.simplified.sdk.SimpleConnectedSystemTemplate class which seems to be correct according to the appian documentation.
Thank you.
Discussion posts and replies are publicly visible
Check your build dependencies.https://docs.appian.com/suite/help/25.2/integration-sdk-versions.htmlhttps://docs.appian.com/suite/help/25.2/develop-first-connected-system.htmlExample for reference : https://github.com/appian/integration-sdk-examples
The version of the connected-system-core and connected-system-client jars are correct and my class is very similar to this example github.com/.../GoogleDriveSampleConnectedSystemTemplate.java and it still gives the same error when deploying
Try adding jar configuration setting(mentioned in screenshot) then rebuild and test.If it still fails, Verify JAR structure
Thank you very much, for your help, I think the issue is resolved.
What was the issue?
I was generating the jar file without gradle, very bad from me. I know it is in appian documentation to set a gradle project, but I thought it was only a recomendation, sorry.
Oh, I was expecting that since it generally gets missed, so I included the documentation link in my first post.
Great to know that you’re good to go!
Hello, I am getting the jar file with build jar and it is ok, but the source files are not included and when I try to submit the new jar I am getting this error
soc..........JAR – 4.09 MB
I have upgraded the gradle version to 9 and included in my gradle.build file this:
jar { duplicatesStrategy = DuplicatesStrategy.FAIL into('META-INF/lib') { from(configurations.runtimeClasspath) } // Include compiled classes and resources from sourceSets.main.output // Include the java files inside the jar from(sourceSets.main.allSource.srcDirs) { include '**/*.java' // Optional: where to include the sources files inside the jar into 'sources' } manifest { attributes("Spring-Context": "*;publish-context:=false") }} now I have inside the jar in the sources folder the java sources files.
Yes, that's correct. Requires source code in plugin JARs for security review/validation. Putting sources in a separate 'sources' folder within the JAR avoids duplication conflicts with appian-plugin.xml.