Unable to create 'HipChat' addon on Marketplace

[Debanshu Kundu]

We are facing an issue with Add-on descriptor while trying to register our production environment descriptor on Atlassian Marketplace (we already have a dev environment add-on registered, which is exactly the same as the production one except for the URLs to various resources).

Here is our descriptor for production env: https://app.hyfy.io/hipchat/descriptor/

When we try to validate this descriptor here http://atlassian-connect-validator.herokuapp.com/validate?product=hipchat, it gives us following errors:

``````````````````````

Root

Description

additionalProperty "baseUrl" exists in instance when not allowed

Root

Description

additionalProperty "authentication" exists in instance when not allowed

capabilities.action[1].conditions[0]

Description

is not of a type(s) [object Object],[object Object]

capabilities.action[2].conditions[0]

Description

is not of a type(s) [object Object],[object Object]

capabilities.glance[0].conditions[0]

Description

is not of a type(s) [object Object],[object Object]

``````````````````````

The first two errors can be resolved by simply removing the "baseUrl" and "authentication". But if we do that we get following error while creating the add-on on Marketplace.

```
The .json descriptor provided is invalid (object has missing required properties (["authentication","baseUrl"])). Check your descriptor and try again.
```

Also, the other three errors shouldn't occur as the we are following the format for conditions in actions and glances specified here https://www.hipchat.com/docs/apiv2/actions and https://www.hipchat.com/docs/apiv2/glances and also the format give in this example https://developer.atlassian.com/hipchat/guide/actions#Actions-Actionconditionsforcards (see the second 'metadata' example).

And even when we try to create the add-on ignoring the above issues, Marketplace only gives us option to choose either 'JIRA' or 'Confluence' as compatible applications and doesn't show us the option to choose 'HipChat'. So we are unable to register our production environment add-on on marketplace.

We even tried to register using this descriptor URL https://marketplace.atlassian.com/files/1.1.2-AC/artifact/descriptor/e3dde6ef-2f3a-42d6-80cb-9fe6528a2722/atlassian-connect.json, which is the descriptor URL of our already registered dev env add-on, which has 'HipChat' added in the product compatibility (https://marketplace.atlassian.com/manage/plugins/com.hyfy.dev.hipchat-addon/versions/1001002/compatibility

). And still wasn't able to select 'HipChat' as compatible product while the creation, as HipChat was disabled and only 'JIRA' and 'Confluence' were selectable. There seem be an issue on the add-on creation form in the Marketplace which is preventing us from selecting HipChat. Please look into this issue and try to resolve it or suggest a workaround to us. We need to publish our add-on as soon as possible.

[Tanguy Crusson]

Hi again,

It looks like you found a bug in marketplace when listing HipChat add-ons. We're on it, and you can track the resolution here: https://ecosystem.atlassian.net/browse/AMKT-15428

As Patrick said: please remove "authentication" and "baseUrl", the rest looks fine.

We'll fix the validator for the error you're getting for action conditions (your descriptor is fine on that front).

[Tanguy Crusson]

The issue should be fixed now.

[Mikhail Vasilyev]

Hi!

I've faced the same issue. The descriptor URL is https://api.dev.message.io/hipchat/descriptor/4466667357555878f127f and I get the same error

The .json descriptor provided is invalid (object has missing required properties (["authentication","baseUrl"])). Check your descriptor and try again.

The Atlassian Connect Validator says everything's okay.

[Patrick Streule]

Hi Debanshu,

We recently added a strict validation mode to the validator that should make it easier to catch elements that were put in the wrong place or typos in attribute names. The results of this check should be treated as warnings, not errors. authentication and baseUrl are not used in HipChat descriptors and are thus flagged as extraneous.

I'll look into why the conditions are reported as warnings.