apurvabhansali
apurvabhansali
we also never had any issues before 130.0.2849.46. Today, multiple customers using our extension are reporting it is not working. When we debug it is the same issue. When we...
Hi, this is happening in customer production environments where the browser just got updated to 130.0.2849.46. I performed the same update on my own laptop and am seeing the same...
Ok, some more steps. When I bring up the browser I am currently in this situation with profiles (this is when I click the profile icon in the top left...
same problem in v131 dev channel browser. Only difference is that I don't see this phantom profile 1 and when I click the icon in the top right corner. Basically,...
And just to re-iterate, this was all working fine before our customers (and myself) upgraded to v130 on stable production browser. Also, no issue on Chrome after V130 upgrade.
I have a 3rd customer with 100+ employees that are all affected by this 130.0.2859.46 release breaking our extension. We use the managed storage api so that enterprise customers can...
@mkruger-msft @ManikanthMSFT is it possible to get a status update on this issue? Has your team been able to recreate the issue and any ETA on a fix? As you...
> [@ManikanthMSFT](https://github.com/ManikanthMSFT) we have recently found the same issue. It looks like in our case 129 was working fine, 130 was broken again, and then the current dev 131 seems...
My observation is that it is not just after fresh install. If you delete your profile and restart edge, then it will work fine the first time, but then after...
> Hey [@apurvabhansali](https://github.com/apurvabhansali), we are currently looking into the issue and will update you as soon as we have more information. > > We appreciate your patience in the meantime....