Skip to main content
Solved

Using latest Package SDK / IntelliJ, Get package.invalid.signature when importing new package?

  • May 8, 2026
  • 2 replies
  • 55 views
DeLo
  • DeLo
  • Navigator | Tier 3

I’m using the latest Package SDK (A360-package-sdk-2.13.0.zip) in IntelliJ, Java 11, Gradle 7.6.2.

I’ve created packages in the past using an older SDK, they all import just fine.

I was wanting to start using the latest Package SDK. So today when I start from the latest Package SDK. It compiles perfectly. Then I get a package.invalid.signature error when importing the new package into the Control Room?

Any ideas?

Best answer by DeLo

The signature verification error occurs when uploading custom packages that contain headless agent targeting (allowed_Agent_Targets = AllowedTarget.HEADLESS) to the Control Room. There is a restriction that prevents uploading custom packages with headless agent targeting unless they are digitally signed by Automation Anywhere. This parameter is automatically included in all custom packages designed to work with API Tasks.

Next steps:- Please ensure that the custom package does not contain the headless agent targeting parameter. Once this parameter has been removed from the package, it can be uploaded to the Control Room successfully.

2 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Aaron.Gleason
  • Automation Anywhere Team
  • May 8, 2026

​@DeLo I noticed this too. It appears all packages must be signed by Automation Anywhere. I would recommend starting a support ticket by emailing support@automationanywhere.com and see if they can disable the signature requirement for your control room instance.

DeLo
  • DeLo
  • Author
  • Navigator | Tier 3
  • Answer
  • May 14, 2026

The signature verification error occurs when uploading custom packages that contain headless agent targeting (allowed_Agent_Targets = AllowedTarget.HEADLESS) to the Control Room. There is a restriction that prevents uploading custom packages with headless agent targeting unless they are digitally signed by Automation Anywhere. This parameter is automatically included in all custom packages designed to work with API Tasks.

Next steps:- Please ensure that the custom package does not contain the headless agent targeting parameter. Once this parameter has been removed from the package, it can be uploaded to the Control Room successfully.

Terms & ConditionsAccessibility statement