feed: compare historical px with listing px about sneaky HOT 4 CLOSED

As it turns out the current version / api endpoint we use does not have historical transaction price in its response: we only have time, size and buyer.
We played around with version string in request header and get params, but didn't get a different response.
Presumably it's the API endpoint that matters.
https://m.poizon.com/product/lastSoldList? --> https://app.poizon.com/api/v1/app/product/ice/lastSoldList
Our current sign value does not work with the second api endpoint: 500 or 403 are both triggered.

from sneaky.

It could also very well be the app version.
The new version presumably has a different sign mechanism, or maybe just a different salt value.
We could try reverse engineering a newer apk.

Some sources:
https://www.jianshu.com/p/652a1722378e
http://www.javadecompilers.com/apk
https://github.com/skylot/jadx

from sneaky.

/Users/zhehaowang/projects/du/reverse-engineering/com.shizhuang.duapp_4.11.1_liqucn.com/sources//com/shizhuang/duapp/common/utils/al.java seems to be the sign generation function.
We didn't manage trace up from requests yet. This is tracing down from i.k in com.shizhuang.duapp.common.a.i where the constant 3542e676b4c80983f6131cdfe577ac9b was still in use.
Two static functions one with param map the other with an additional timestamp. Need to figure out under what circumstances each is used.

from sneaky.

We switched to a different wechat small program based interface described here
https://github.com/luo1994/du-app-sign

from sneaky.