Unable to Enable Add-on (NodeJS)

Developer General
1

Hey All

Have a small issue affecting clients trying to enable a new Simple NodeJS Addon, when thye click the Private Add-on Install URL they are fowarded to the addon store page, insted of the traditonal Approved Unverified Addon Screen

I have tried to recreate the addon by uploding the Manafest and the Function to a fresh addon, and it affects the new addon too.

Anybody else experiencing this issue?

1 Like
2

Yup, exact same issue. It seems to depend on the target system it is attempted to be installed on; on some the install URL works fine, on others it presents the addon store page.

3

Hi Nick and Franco,

Thanks for flagging this. We found the affected accounts were running an older ServiceM8 version and have now upgraded them.

Please retry the Private Add-on Install URL. It should now open the expected approval screen.

Cheers,
Cody

4

Hi there Cody

I’m still seeing the same behaviour for an account based in the AWS region us-west-1

5

Thanks for the update, logged out and back in and now it is working on the accounts i was experiencing issues with.

6

Likewise; it’s back to normal now

7

Hi Nicholas,

For a Simple Function Add-on (NodeJS), the documented development/testing path is to set the add-on type, upload the manifest, save it, then connect it from Settings > ServiceM8 Addons in the Custom Addons section. The developer docs also say the Private Add-on Install URL is used to share an add-on pre-approval during testing.

If the Private Add-on Install URL is redirecting client/test accounts to the Add-on Store page instead of allowing the install/connect flow, that’ll need an add-on-specific check rather than troubleshooting the private URL publicly. Product help can be raised through the Help menu in the Online Dashboard.

Send the add-on name or developer add-on UUID, plus a screenshot of the redirect, to ServiceM8 Support via the Help menu so we can review it privately.

Thanks,
Cody