Version 1.80.1 is not working

[BennyBrowns]

Hi team,

The plugin stopped working after the automatic update yesterday to 1.80.1 (Latest). The loading bar keeps showing and different errors are logged in the browser console (e.g. CORS).

Can you please check this? Thank you very much!

Kind regards.

[Jegge]

Same problem here. We use the plugin on a local installation and it thinks that it's backend service URL is https://app-retrospective-extension-prod.azurewebsites.net. Shouldn't this be our local server?

[danielabreu-cotacao]

Same problem here.

[Yozya]

Same problem.

[IRQG]

Hi, I'm experiencing the same problem on Azure on premise 2019. Error from js console Access to fetch at 'https://app-retrospective-extension-prod.azurewebsites.net/collaborationUpdates/negotiate?negotiateVersion=1' from origin '' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

[gabrielgdomingos]

Same problem.

[shariqueshueb]

Same problem

[TejalVV]

Has anyone found the solution ?

[danielabreu-cotacao]

I did a rollback on my environment.

[kpworld]

I did a rollback on my environment. @danielabreu-cotacao

What type of rollback? a full rollback or of the extension itself? Haven't seen a way to do a rollback of one of MS built extensions or the best way to accomplish that. Any help is appreciated.

• I did notice there was activity on this. Hoping it resolves the issue with an update vs. having to go backwards.

[danielabreu-cotacao]

I downloaded the old version on this url: https://marketplace.visualstudio.com/_apis/gallery/publishers/ms-devlabs/extensions/team-retrospectives/1.70.6/package?noPrompt=true, opened the file with 7zip and changed the version inside the file extension.vsixmanifest to a version above the current one. After that updated manually Azure DevOps with this "new" version.

[gabrielgdomingos]

How did you find this link to download the extension?

This manual update would be through the 'Browse local extensions' button, right?

@danielabreu-cotacao

[polatengin]

hi @BennyBrowns , @Jegge , @danielabreu-cotacao , @Yozya , @IRQG , @kpworld , @gabrielgdomingos , @shariqueshueb , @TejalVV

first of all, sorry for the inconvenience, I wasn't expect to have an issue with the sync service.

I was testing and playing with the new version on my dev environment for a quite time.

I just fixed (at least I think I fixed) the issues, and, release a new version (v1.80.4) to the production environment.

I'll keep this issue open for a week, to collect the feedbacks, hopefully there will be not much feedbacks 😄

this new version I just released must solve the issues you have.

please let me know, if I can make the extension better anyway.

[Yozya]

Still have an error "Access to fetch at 'https://app-retrospective-extension-prod.azurewebsites.net/collaborationUpdates/negotiate?negotiateVersion=1' from origin '' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

[Guyzigi]

Hi polatengin this issue still occurs in our environment, ver 1.80.4

[kpworld]

Hi polatengin this issue still occurs in our environment, ver 1.80.4

We as well continue to see the same issue as shown in the screenshot.

[ka-kalee]

Same problem in our environment as well in ver 1.80.4

[kpworld]

@pol

hi @BennyBrowns , @Jegge , @danielabreu-cotacao , @Yozya , @IRQG , @kpworld , @gabrielgdomingos , @shariqueshueb , @TejalVV

first of all, sorry for the inconvenience, I wasn't expect to have an issue with the sync service.

I was testing and playing with the new version on my dev environment for a quite time.

I just fixed (at least I think I fixed) the issues, and, release a new version (v1.80.4) to the production environment.

I'll keep this issue open for a week, to collect the feedbacks, hopefully there will be not much feedbacks 😄

this new version I just released must solve the issues you have.

please let me know, if I can make the extension better anyway.

@polatengin the 1.80.4 version did not fix our issues. Are you currently looking into further solutions?

[dstoddar]

@polatengin

[BennyBrowns]

Hi @polatengin. Version 1.80.4 is not working on our environment (on premise server 2019). The same error still occurs.

Can you recheck this?

Thanks in advance! Kind regards.

[pollpbl]

TFS 2018 U3 also doesn't work anymore. Thanks in advance!

[denitajc]

This still isn't working on our TFS 2018 on premise server

[denitajc]

I downloaded the old version on this url: https://marketplace.visualstudio.com/_apis/gallery/publishers/ms-devlabs/extensions/team-retrospectives/1.70.6/package?noPrompt=true, opened the file with 7zip and changed the version inside the file extension.vsixmanifest to a version above the current one. After that updated manually Azure DevOps with this "new" version.

I was not able to get this to work. When I changed the version inside the extension.vsixmanifest to a version above the current one it gave me an error when I tried to update the file about a corrupt manifest. Has anyone else been able to rollback using the method described here?

[gabrielgdomingos]

I downloaded the old version on this url: https://marketplace.visualstudio.com/_apis/gallery/publishers/ms-devlabs/extensions/team-retrospectives/1.70.6/package?noPrompt=true, opened the file with 7zip and changed the version inside the file extension.vsixmanifest to a version above the current one. After that updated manually Azure DevOps with this "new" version.

I was not able to get this to work. When I changed the version inside the extension.vsixmanifest to a version above the current one it gave me an error when I tried to update the file about a corrupt manifest. Has anyone else been able to rollback using the method described here?

You should not extract the entire zip, extract only the extension.vsixmanifest file, change the version and then put the edited file in the zip again replacing the current one. If you want, follow the link to download a version "2.0.0". https://1drv.ms/u/s!AvnQGG2Tx82sgqwFv6nRBuAJqJt04g?e=4LhtTe

[denitajc]

Thank you that worked. I appreciate the quick response.

[ka-kalee]

Version 2.0.0 work on ADO 2019.

[gabrielgdomingos]

A versão 2.0.0 funciona no ADO 2019.

Yes, this version 2.0.0 is actually version 1.70.6 masked.

[kpUniverse]

Other than rolling back, is there any further progress on resolving the current issue? @polatengin @dstoddar

[dstoddar]

@kpUniverse , we are currently debugging. Are you able to upgrade your server? We have not isolated the root cause yet and it's recommended that you upgrade.

[kpUniverse]

@dstoddar

We are not able to upgrade in the near term. That is a longer term process to complete and not on the radar right now.

will look to using the downgrade fix above next week if you haven't yet figured out the issue in your debugging.

Thanks!

[klsgrtx]

@dstoddar - we are also not in a position to upgrade to ADO 2020. Running ADO 2019 and have numerous users unhappy about retrospectives not working.

Do you have instructions for rolling back? As we are concerned with possible corruption of data.

Our install stopped working on July 12, when we updated retrospectives from 1.70.6 to 1.80.4

[reavild1]

My enterprise is among the victims. Did the release that broke this provide so much value that it could not be rolled back? ADO Server 2019 using http: protocol for DevOps web

[dstoddar]

@reavild1 , @klsgrtx , @kpUniverse , @BennyBrowns , @Jegge , @danielabreu-cotacao , @Yozya , @IRQG , @kpworld , @gabrielgdomingos , @shariqueshueb , @TejalVV.

Please accept our sincerest apologies for the inconvenience this issue has caused, and thank you for raising visibility and helping us identify the root cause. We have successfully reproduced the issue on our end and @polatengin us focused on isolating the root cause and coming up with a fix. We are hopeful that this fix will be in place in the next few days but can't be certain of the timeframe until we fully identify the root cause. Thank you again for raising the issue and helping us debug it to this point.

[dstoddar]

@reavild1 , @klsgrtx , @kpUniverse , @BennyBrowns , @Jegge , @danielabreu-cotacao , @Yozya , @IRQG , @kpworld , @gabrielgdomingos , @shariqueshueb , @TejalVV.

We believe we have isolated and resolved this issue. If you continue to have any issues related to this bug please contact @polatengin directly. Thank you for your patience.

[gabrielgdomingos]

@reavild1 , @klsgrtx , @kpUniverse , @BennyBrowns , @Jegge , @danielabreu-cotacao , @Yozya , @IRQG , @kpworld , @gabrielgdomingos , @shariqueshueb , @TejalVV.

We believe we have isolated and resolved this issue. If you continue to have any issues related to this bug please contact @polatengin directly. Thank you for your patience.

here solved

[danielabreu-cotacao]

here solved too.

[kpUniverse]

I'm waiting on it to show up in the system as updated. How long does it normally take? Or is there a way i can speed that along? appreciate your efforts at tracking down the issue. Hoping it fixes ours as well once i can get it in place

@polatengin

[Yozya]

@dstoddar @polatengin thank you for your work.

[kpUniverse]

The latest showed up and it is working again. Thanks for working through the problem and providing a solution. @dstoddar @polatengin

[klsgrtx]

We have deployed the latest (1.80.10) to our 2019 on-prem instance - all appear to be working well.

[Mi1an]

We have the version 1.80.11 on our DevOps 2019 and it's still not working. Should we wait for a fix or should we make a downgrade to the version 1.80.10?

[dstoddar]

We have the version 1.80.11 on our DevOps 2019 and it's still not working. Should we wait for a fix or should we make a downgrade to the version 1.80.10?

@polatengin , please advise.

[nordic81]

We had the same problem, but completely uninstalling and reinstalling the extension did the trick. Try removing the extension from your collection and removing it from your onprem installation. Than you can reinstall it via the marketplace and hopefully everything works as expected ;)

[Mi1an]

We had the same problem, but completely uninstalling and reinstalling the extension did the trick. Try removing the extension from your collection and removing it from your onprem installation. Than you can reinstall it via the marketplace and hopefully everything works as expected ;)

Unfortunately this didn't helped us. Retrospectives still not working.