Microsoft-Reward-Chrome-Ext
Microsoft-Reward-Chrome-Ext copied to clipboard
Icon turns red, when clicked turns back to blue but doesnt do searched
This is the error I am getting.
I am on chrome, mac os
Any ideas on how to fix this?
I'm having the exact same error since a week ago aprox. Since it, it is not doing the searches. Not working anymore.
I'm on W11 fully updated. Extention is on chrome fully updated as well.
any help would be gladly appreciate.
Same thing happened to me, would also like some help if anyone has it.
I did some modified to do search quests with PC and then Mobile agent one by one. I just wanted to let you know that it works for me so far.
What did you do exactly?
do you mind sharing the fix? It is still not working for me.
also having this issue and would love to know if anyone has a fix!
where the devs at
I did some modified to do search quests with PC and then Mobile agent one by one. I just wanted to let you know that it works for me so far.
Would you mind sharing your fix?
https://github.com/XxBAJNOKxX/Microsoft-Reward-Chrome-Ext/releases/tag/v2.24.6 The above with latest user agents update works with Edge, no working fix so far for chrome I think
no working fix so far for chrome I think
I use on edge, on DevTools console only show useragent, and on network tab show search activity but no point added.
then I try on Chrome, It work really smooth.
edit: I think dev forgot change version on something. that release 2.24.6 show as 2.24.5 on my extension.
I'm sorry guys I cannot make it work. I try the v2.24.6(5) con chrome and edge and I could not make it work. I do not find "only show useragent" nor something similar. Also, I could not find the network tab to verify if I should change something there...
Could someone that make it work please take a few min to specify the steps for rookies? Thank you very much!!
Could someone that make it work please take a few min to specify the steps for rookies? Thank you very much!!
steps to show network tab? click this, it will open new window, and show developers tools
Any updates here? I am having the same issue with MacOS and Chrome
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 valid searches.
I'll try to find a solution for this.
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
Thanks again Bajni
The randomness implementation in v2.25.0 of banjo's fork is bugged, it does not use hex/base16 and it may get you caught by Microsoft so be careful, I have opened a pull request on the fork to fix the mildly large oversight. Hopefully the pr does get accepted and nobody gets caught.
this was fixed in v2.25.1 and you can now use the extension with less risk of being detected.
this was fixed in 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 and you can now use the extension with less risk of being detected.
This one gives me a red icon :(
Please send us/me the error message
this was fixed in v2.25.1 and you can now use the extension with less risk of being detected.
This one gives me a red icon :(
Please send us/me the error message
It's Failed to load resource: net::ERR_BLOCKED_BY_CLIENT and the exact same errors as the beginning of the post. Your previous version did work but as stated by david that one is unsafe in terms of being detected?
I know that isn't the issue, can I have a look at the network tab? more specifically selected on any bing search request.
I know that isn't the issue, can I have a look at the network tab? more specifically selected on any bing search request.
And this is from a random Bing search:
this was fixed in v2.25.1 and you can now use the extension with less risk of being detected.
This one gives me a red icon :(
Please send us/me the error message
It's Failed to load resource: net::ERR_BLOCKED_BY_CLIENT and the exact same errors as the beginning of the post. Your previous version did work but as stated by david that one is unsafe in terms of being detected?
Do you have any other extensions installed?
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 you fixed it after releasing v2.25.1.
the solution for @Forsefrits would be to update to v2.25.1.1 as it doesn't quite use the same method and the typo has since been fixed.
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 you fixed it after releasing v2.25.1.
the solution for @Forsefrits would be to update to v2.25.1.1 as it doesn't quite use the same method and the typo has since been fixed.
Yes it is working now, thanks a bunch! :) Amazing job by the way, this plugin, thank you very much
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 you fixed it after releasing v2.25.1.
the solution for @Forsefrits would be to update to v2.25.1.1 as it doesn't quite use the same method and the typo has since been fixed.
Version v2.25.1 has been fixed. Sorry everyone :(
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 you fixed it after releasing v2.25.1.
the solution for @Forsefrits would be to update to v2.25.1.1 as it doesn't quite use the same method and the typo has since been fixed.
Version v2.25.1 has been fixed.
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?
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 an unknown reason, try to open another browser and import the extension there. But it should be fixed within a few days.