microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
180 stars 80 forks source link

Retrospectives version 1.8.10 still not loading for TFS 2018 U 3.2 #400

Open denitajc opened 2 years ago

denitajc commented 2 years ago

Retrospective still is not working after the 1.8.10 update

denitajc commented 2 years ago

@polatengin - The retrospective is still not loading for TFS 2018 u 3.2

dgdavidt commented 2 years ago

@mindlessroman - We are also not able to load the new version of Retrospectives v 1.8.10 in onprem TFS 2018. Please help to route this issue to the right team to help fix this issue.

The error message says: "Retrospectives by Microsoft DevLabs failed to load. Learn More http://xxx.local.xxx/tfs/_gallery/items/ms-devlabs.team-retrospectives about this extension, including available support options."

image

tbeavers commented 2 years ago

Getting the same error when trying to use version 1.80.11 with TFS 2018 Update 2 (Version 16.131.27701.1).

Please advise.

Thanks for your support.

nashda commented 2 years ago

We are seeing the same error using TFS 2018 Update 2 (16.131.28507.4) and Retrospectives version 1.80.11. The following error is seen in the console, if relevant. Tried uninstalling and reinstalling multiple times. No joy.

DevTools failed to load source map: Could not load content for https://[redacted]/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/team-retrospectives/1.80.11/assetbyname/dist/reflect-bundle.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load source map: Could not load content for https://[redacted]/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/team-retrospectives/1.80.11/assetbyname/node_modules/applicationinsights-js/dist/ai.0.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

vishalgpt38 commented 2 years ago

The retrospective is not loading for TFS 2018 3.2. Could you please help us to fix this issue. image

brandonsmiller486 commented 2 years ago

Any chance anyone from microsoft can give us an update here? ALL of our retro data is stored here and nowhere else, and we can't even figure out a back door to get it out.

dgdavidt commented 2 years ago

The Contributors have been troubleshooting and responding to similar issue in #371 and #380

cc @dstoddar - #400 is having the same error reported error.