Install event calling //install and returning 404 error on install

It looks like there’s been a change to the /install event which is causing installation failures.

Instead of calling /install, it’s now calling //install and returning a 404 error.

Does this mean we should change our reference to the install event from /install to install in our atlassian-connect file?

Hi @RhysDiab,

  1. Are you saying we are calling your app’s install end point at {baseUrl}//install instead of {baseUrl}/install?
  2. Is this happening consistently for multiple tenants?
  3. Do you define your {baseUrl} with a trailing ‘/’?

I don’t think there has been any intentional change by Atlassian.

Regards,
Dugald

Hi @dmorrow.

Thanks for the quick response.

  1. That’s correct.

  2. It’s happening both when I run the app locally and in production. When I try to install the app on the marketplace, it won’t install, and the logs indicate it’s calling //installed.

  3. Yes I do. It hasn’t caused a problem up till now. If this is now an issue I can change it.

I saw in another thread there were changes being made to the fields returned from the /installed event, maybe something else was changed accidentally?

Let me know what you think the best way forward is.

Regards,
Rhys

Thanks @RhysDiab,
There were no code changes associated with the other thread. The engineers who maintain the installation code are not aware of any changes. We will continue looking into this.
Regards,
Dugald

Hi @RhysDiab,
After further investigation we still have not found any changes on our part. Is there a chance there could have been a change at your end? Maybe something subtle like a server config change causing less lenient URL parsing? Of course, you could test the removal of the trailing slash on your app descriptor’s baseUrl, but be aware of all its dependencies and that this will require a change in the Marketplace listing which takes hours to roll out to all tenants.
Regards,
Dugald

Thanks for looking into this @dmorrow.

It may well be from a change on my end. I did a deploy yesterday, but everything was working all yesterday after the deploy, including a number of new trials where the correct URL was called (’/installed’). But yes, completely possible I’ve goofed up somewhere.

I think I’ll change the install url from ‘/installed’ to ‘installed’ as this seems to fix the issue and only causes a minor update.

Thanks again, I really appreciate you looking into the issue.

UPDATE: Just checked. This issue is also occurring on older branches before my last release.

Regards,
Rhys

Thanks for the update now. We’ll close our side of the investigation for now.
Regards,
Dugald

I’m seeing the same issue as @RhysDiab. Everything was working fine when I shut down yesterday evening, but the app wouldn’t register at all this morning. I did some digging and came to the same conclusion – the marketplace is calling //installed instead of /installed.

I was able to repeat this by creating a new app with atlas-connect and following the basic instructions to get the dev loop running. Removing the slash from the atlassian-connect file gets around the problem, but that’s not documented anywhere.

I don’t know what changed, but that extra slash is causing problems.

Same problem started happening for me today too, with no any chances.

Also got this issue. Even my apps that I haven’t touched for months (but were still working at the time) are still registering this //installed 404 error.

Something’s definitely been changed in the registration process.