Bajni✨

**The repo is not up to date with current useragents.** - You can fork the repo, and change the useragents [here](https://github.com/tmxkn1/Microsoft-Reward-Chrome-Ext/blob/master/useragents.json) and edit the utility.js file [here](https://github.com/tmxkn1/Microsoft-Reward-Chrome-Ext/blob/8f265eb224915221e1ba7302f97db171c1ae422a/src/utility.js#L142) to your own...

> Still not working for me. it starts after chrome update 2 days ago. Which troubleshooting method have you tried?

Okay, so it looks like Microsoft has started using unique identifiers for searches. Searches used by the extension do not contain these unique identifiers and are therefore not considered as...

I have a temporary solution: https://github.com/XxBAJNOKxX/Microsoft-Reward-Chrome-Ext/releases/tag/v2.24.8.pre **Probably until I solve the whole problem, the extension needs to be updated every 2 days**

> > this was fixed in [v2.25.1](https://github.com/XxBAJNOKxX/Microsoft-Reward-Chrome-Ext/releases/tag/v2.25.1) and you can now use the extension with less risk of being detected. > > This one gives me a red icon :(...

> > > > this was fixed in [v2.25.1](https://github.com/XxBAJNOKxX/Microsoft-Reward-Chrome-Ext/releases/tag/v2.25.1) and you can now use the extension with less risk of being detected. > > > > > > > >...

> uh, @XxBAJNOKxX > the v2.25.1 release still contains that one typo with the "numbers" var being typed out as "number" even though you had fixed it. > i think...

> uh, @XxBAJNOKxX > the v2.25.1 release still contains that one typo with the "numbers" var being typed out as "number" even though you had fixed it. > i think...

> This seems to have fixed the mobile searches for me, however the desktop searches and bing searches are not working yet, is that just me? Browsers do this for...