microsoft / azure-pipelines-jira

Azure Pipelines for Jira
MIT License
15 stars 6 forks source link

Get started results in "App is not responding" message being displayed indefinitely #6

Closed spr0ut closed 4 years ago

spr0ut commented 5 years ago

Describe the bug Once installed, clicking the Get started button results in the message "App is not responding. Wait or cancel?" being displayed indefinitely.

To Reproduce

Expected behavior Some configuration screen should load.

Screenshots If applicable, add screenshots to help explain your problem. image

Uninstalling and reinstalling resulted in the same behaviour.

User account installing the application is both a JIRA admin and Azure Devops org admin.

spr0ut commented 5 years ago

Can someone respond to this issue please? @shashban / @shyama1208

shashban commented 5 years ago

@prativen for diagnosis of the issue

prativen commented 5 years ago

@spr0ut Apologize for having missed this. Can you send us a HAR file for your session to help us diagnose the issue you are facing. You could write to us at RM_Customer_Queries @ microsoft.com with a link to this issue and the file. Thanks!

spr0ut commented 4 years ago

It appears a recent update has resolved this issue.

sanjusoftware commented 4 years ago

doesn't look like this issue is resolved yet. I am facing the same issue today. After multiple install / un install / reinstall cycles, I am still getting the same message even after waiting for more than 30 mins... please help me resolve this issue.

image

andyworsley commented 4 years ago

I had the same issue as @sanjusoftware today.

shashban commented 4 years ago

Can you please report this as an issue at https://developercommunity.visualstudio.com/spaces/21/index.html?

andyworsley commented 4 years ago

@shashban Done, here is the problem I have reported: https://developercommunity.visualstudio.com/content/problem/988244/azure-pipelines-for-jira-hangs-at-get-started-conf.html. Can you please expedite the problem, as I am keen to get this working ASAP?

andyworsley commented 4 years ago

@shashban Looks like this has been reraised as #33.