Invalid mobile fingerprint: Android UA mixed with macOS desktop signals #458
Description
The generated mobile fingerprint is not realistic and is easily detectable as spoofed. It combines Android mobile identifiers with macOS desktop platform data.
Issues identified:
navigator.platform reports MacIntel while UA is Android
sec-ch-ua-platform is "macOS"
WebGL renderer shows Apple M2 (Metal) (desktop-only)
sec-ch-ua-mobile incorrectly set to ?0
Desktop resolution and zero viewport values
No touch support (maxTouchPoints = 0)
Desktop PDF plugins and macOS fonts present
When convenient, could we consider improving mobile device profiles so mobile sessions more closely reflect real phones? This would really help with consistency and reliability.