Problem Enabling UserAgent-Switcher

[warrenweiss]

Recently, I have been unable to set a user agent unless I disable the extension, then re-enable it.

Upon trying to enable it, the banner indicating successfully setting the agent is displayed, but the agent is not correctly set.

When I disable the extension, then immediately re-enable it and set the agent to a value, it does correctly set it.

I am using Firefox 146.0 for Linux Mint currently, but I noticed the same behavior with v145.

[ray-lothian]

It could be a conflict with another extension. Could you try testing it on a clean browser profile to confirm?

[warrenweiss]

I'll check it

[warrenweiss]

I copied the main profile to another (and named it "extensiontesting") and systematically disabled all other extensions, but the behavior remains. One difference is though that, once the extension is enabled and working, I can change to different agents successfully.

What may or many not be important is that I didn't see any reference to Agent Switcher in the "prefs.js" file, unless it's mention by a different name.

[BillAnt1]

I've noticed this too, especially after doing a "Reset" and "Apply to all Windows".
When using the UA-Switchers build-in "Test-UA" tool, it's showing the browser's original UA, but if you check it with an external checker like https://www.esolutions.se/whatsmyinfo its showing the correct UA. For good measure I usually disable and re-enable the extension, though it's probably not necessary.
I use a custom mode/list too but not random, just per site and the default UA is set in the drop down menu for all other sites.
As a curious note, for Cloudflare and a couple of other sites, I must set the UA to v111.0.0.0, otherwise the Cloudflare checkbox test fails, it's pretty puzzling.

{
"cloudflare.com, godaddy.com, ups.com": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36"
}

[ray-lothian]

I copied the main profile to another

Please try testing this on aclean profile instead. Copying a profile doesn't behave the same way.
Also, if you can reproduce the issue on a clean profile, it's much more likely that I'll be able to reproduce it too.

When using the UA-Switchers build-in "Test-UA" tool, it's showing the browser's original UA

@BillAnt1, What does navigator.userAgent show in the browser console on the test page?
Is the spoofing working correctly or not?

[BillAnt1]

@BillAnt1, What does navigator.userAgent show in the browser console on the test page? Is the spoofing working correctly or not?

It seems to be happening when I click on Reset or Restart, it shows the browser's built-in UA instead, but only on your test site. If I check it via another UA checker site, it's showing the correct new UA. It's more of a cosmetic issue, and the way fix it is by toggling between "Black-list" and "White-list" from the extension's menu, then also your test site shows the correct new UA.
When the glitch happens, all the variables including navigator.userAgent show the browser's built-in UA till I do the Black/White list toggle.

The following is unrelated to the above, I use the Custom Mode and I have a couple of sites configured to use a specific UA, while all others to use another one via the "*": "UA string". I was wondering if it would be possible to use the browser's own built-in UA for specific sites?
There are a couple of websites which do not work with any user defined UA's, and I'd like to set it in the Custom Mode to use the browser's built-in UA instead. If I specify the exact built-in UA string as a custom entry for specific sites, it's showing the correct original UA but some sites won't work when a script generates the original UA. But it works fine if I disable the UA-Switcher extension or select White-List mode with no entries specified. Any way to set an exception in Custom Mode to show the browser's built-in UA for specific sites, yet still use the "*": "UA string" for all others?

[ray-lothian]

Reset or Restart, it shows the browser's built-in UA instead

Reset button resets the extension so the UA is back to default. Anyhow I am still not able to reproduce the issue. Please provide steps if you can generate the issue on a clean browser profile

Any way to set an exception in Custom Mode to show the browser's built-in UA for specific sites, yet still use the "*": "UA string" for all others?

This is what blacklist mode does. I am not sure why you are on the custom mode.

If I specify the exact built-in UA string as a custom entry for specific sites, it's showing the correct original UA but some sites won't work when a script generates the original UA

Do you have an example? Have you tried appending them to the "Disable Spoofing" list?