Why is /atlassian-connect/ not available on some instances?

[Tom]

On my developer instance of Jira, I can run my atlassian-connect-express addon without any problems.

On my company's instance of Jira, both /atlassian-connect/all.js and /atlassian-connect/all-debug.js are not available and give me 404s which leads to the "App is not responding. Wait or cancel?" message.

What's the difference that makes it work on one but not on the other?

Temporary workaround: I've looked through some other addons that were still working and where they got their resources. These other addons couldn't load via /atlassian-connect/ either, but from connect-cdn.atl-paas.net/, so I've replaced

<script src="{{ hostScriptUrl }}" type="text/javascript"></script>

with

<script src="https://connect-cdn.atl-paas.net/all.js" type="text/javascript"></script>

for now.

But the question still remains, more so because obviously this doesn't automatically switch between all.js and all-debug.js depending on the app's env.

[Matthew Hunter · Accepted solution]

This is likely caused by the deprecation of all.js per https://community.developer.atlassian.com/t/deprecation-of-xdm-e-usage/32768 - this was announced a few months ago and our team reached out to Vendor developers through any channels available to them. We've been gradually rolling out the fix, so some instances are impacted but others aren't (which is why the problem occurs on some instances and not others).

[Tom]

Okay, thanks for clearing things up. We've started development of our app right after the change was announced and created a vendor account just a few weeks ago - so that's probably why the info hasn't reached us.

What I'm asking myself is why the mechanism for hostScriptUrl isn't updated (https://bitbucket.org/atlassian/atlassian-connect-express/src/9f62e803106ccd015c1dd039fa6902c6ca08a2c6/lib/middleware/request.js#lines-8) so that it can switch between all.js and all-debug.js like it used to.