BUG: URL-based app install doesn't completes

[Kartones]

Steps to Reproduce

- Login into your Cloud Jira (I tested with free, don't know if also happens with paid one)

- Go to the Manage Apps section (xxxxx.atlassian.net/plugins/servlet/upm)

- "Settings" -> "Enable Private Listings" & refresh

- "Upload app" -> Paste an app URL (I am using https://marketplace.atlassian.com/files/1.1.3-AC/artifact/descriptor/f9a892e6-c9a2-4a03-933f-c29a8053e3df/atlassian-connect.json from Worklytics: https://worklytics.zendesk.com/hc/en-us/articles/219447907-Jira-Confluence-Integration-Atlassian-Connect-  , updating it before attempting to connect)

- once appears listed I update it to the latest version, then click on "Get Started"

- it navigates to xxxxx.atlassian.net/plugins/servlet/ac/co.worklytics.jira/post-install  and there is where it errors.

Expected result

Jira Cloud renders the iframe with the application post-install steps (in this case a simple page with a button to finish connecting to the application).

Actual result

Page stays loading for a while, ends up erroring:

Inspecting the network calls, the post-install call to the application succeeds, and if I preview it and click on the "Open Worklytics" the app connection is performed successfully.

But up in the network calls there's one 404 error:

Request URL: https://xxxxxx.atlassian.net/rest/api/latest/user/properties/navigation_next_ui_state?accountId=yyyyy
Request Method: GET
Status Code: 404
Body:

{"errors":{},"errorMessages":["The property navigation_next_ui_state does not exist."],"httpStatusCode":{"present":true}}

So while the connection is fine, looks like the UI breaks and doesn't renders the post-install iframe.

Searching around I found this error which is pretty similar, exactly the same error and behaviour, but at another page: https://jira.atlassian.com/browse/JSWCLOUD-20527?

Might be related, so just in case mentioning.

I also tried Confluence Cloud and that one works without issues (same process, url-based app install), so might be only this specific Jira page.

If any further info is needed feel free to ask.

Thanks and regards

[Kartones · Accepted solution]

Self-answering myself: After some debugging, the issue was in our `all.js` (to be specific, `all-debug.js`), it should no longer be hosted as a subdomain-based file, but instead use Atlassian CDN (see https://developer.atlassian.com/cloud/jira/platform/about-the-javascript-api/).

Once I updated the url to the CDN one, it worked fine.