Open garret1317 opened 9 months ago
Thanks for your information. I haven't done reverse-engineering radiko app for a long time. Last time i saw there was a new type aSmartPhone7o
.
I may change this in next regular update (maybe after a few months but no guarantee). Since MV3 , this project is basically a obsolete one. I may not take a lot care of this project.
For the suspicious
topic , there're already plenty of suspicious parts in this project , like HTTP headers (sent by browser forcibly).
version 8 of the mobile app is new and shiny, and uses a different key and device id
you include some 8.0.* releases in the pool of choices for
get_appversion
but if you're sending v7'sX-Radiko-App: aSmartPhone7a
with v8'sX-Radiko-App-Version: 8.0.11
that looks a bit suseasy solution: get rid of the v8s in get_appversion, stay on v7 for the foreseeable future
less easy solution: switch to the v8 key/id you can bin some of the spoofing code if you do that, when i looked the app seemed to use hardcoded
X-Radiko-Device
and user agent (android
andMozilla/5.0 (Linux; Android 10; Pixel 4 XL) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Mobile Safari/537.36
respectively (i don't have a pixel)) v8 key + how i got it here id isaSmartPhone8