new source

[Vader77Darth]

Is it theoretically possible to add 应用汇 as a source to obtanium?

[ryux1]

Yes, theoretically—but it is not a supported source today.

Obtainium can try an 应用汇/AppChina app page through its generic HTML source. That only works if the page exposes links Obtainium can follow to actual APK files; you may need a custom APK-link filter and version-detection settings. The HTML source behavior is documented here: https://wiki.obtainium.imranr.dev/sources/#html

If the page builds download URLs through JavaScript, requires store-app authentication, or returns an intermediate endpoint instead of a usable APK, a dedicated AppChina source would be needed. That adapter would have to reliably extract the current version and downloadable artifact, similar to the existing store-specific sources. The current supported-source list does not include AppChina: https://github.com/ImranR98/Obtainium#currently-supported-app-sources

For a particular app, the quickest test is to add its AppChina web page and inspect the links with the HTML source. If you share that exact app-page URL, someone can determine whether the fallback is sufficient or a new adapter is required.

[Vader77Darth]

http://m.appchina.com/app/com.tencent.mm

How about this app for example? Would a new adapter be required? Just asking so I know if there is any point to asking this source to be added as a feature request.

[ryux1]

For that exact app, a dedicated AppChina source (or a change to the generic HTML extractor) is needed.

I checked the URL today:

• http://m.appchina.com/app/com.tencent.mm resets the connection from a normal client.
• The HTTPS mobile host has a certificate mismatch and redirects to the AppChina homepage rather than the app page.
• https://www.appchina.com/app/com.tencent.mm does expose WeChat 8.0.77 and a working APK response, but the download URL is stored in an onclick="freeDownload(...)" attribute, not an <a href>, and the URL has no .apk suffix.

That combination defeats the current generic HTML source. Its normal path reads anchor href values; “match links outside <a> tags” finds the raw URL, but also captures the trailing HTML entity/markup from this inline handler, and the default APK filter cannot identify the extensionless endpoint.

So yes, there is a point to filing a feature request. Include this exact app URL and mention that an adapter needs to extract the version from the page metadata/title and the APK URL from freeDownload(...). The endpoint itself currently returns application/vnd.android.package-archive, so the underlying artifact is usable once extracted cleanly.

[Vader77Darth]

Thank you.