Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Hardware: Samsung S10 (SM-G973F/DS)
OS: Android 12/One UI 4.1
Software: Steam 3.5/Firefox 111.1.1/Chrome 112.0.5615.48. Firefox set as default browser. No fancy launchers or anything like that.
(side note: I find it interesting that the original post is as old as some bugs i found in the client Beta that still aren't fixed.)
Just decompiled the app (thanks Android for using Java) to see why it does this.
This appears to be a result of using resolveActivity in the OpenLinkInExternalBrowser function in com/valvesoftware/android/steam/community/ValveHelpersModule.java
Since Android 11/API 30, resolveActivity has returned null unless declared in the manifest using <queries>[developer.android.com], which it currently isn't.
Due to this, it will always fall back to com.android.chrome on Android 11+ (maybe also on older devices?), ignoring the user's preferences, or worse, doing absolutely nothing when Chrome is either unavailable or disabled.
So, technically it isn't Valve's fault, but ironically Google's fault in trying to improve privacy. Though, Valve should be checking the docs before targeting a newer API.
I have reported this directly to Steam support. Hopefully they will pass the info on to the Android app team, who can fix it with one small edit to the Manifest.xml