App Cloner

[nOneCode4u]

https://appcloner.app/

I'm unable to add this app to the obtainium list.

[DwainZwerg]

https://appcloner.app/ is loaded with Java-Script. So we can't do anything because Obtainium don't support Java-Script.

[nOneCode4u]

https://appcloner.app/ is loaded with Java-Script. So we can't do anything because Obtainium don't support Java-Script.

When will Obtainium support JavaScript?

[DwainZwerg]

@nOneCode4u Probably not at all. If you feel capable, you can of course create a PR.

[LightWayUp]

https://appcloner.app/ is loaded with Java-Script. So we can't do anything because Obtainium don't support Java-Script.

Obtainium's "HTML" app source type is primarily for scraping HTML documents (files that statically define the web page layout and structure), and it's true that the final App Cloner's page is dynamically generated client-side (in your browser), therefore Obtainium can't extract information from the HTML document at https://appcloner.app/.

However, if a resource isn't valid HTML, or if it is but there are no usable links defined by anchor tags (<a>), Obtainium falls back to text matching. This means any plain-text resources, like .json, .js, .xml, .txt, .md, .csv, .log, even .ipynb if you really want to..., can be scraped by Obtainium.
This is the same reason that #89 - configuration for Droidsound-E works. The Droidsound-E website uses JavaScript to dynamically load information from a JSON file, so we scrape the JSON file directly instead. Whether a page uses JavaScript or not is not the absolute criteria of being handled by Obtainium — the information still has to come from somewhere.

There are 2 limitations of Obtainium that matter here:

1. The initial URL has to be known
   A static initial URL has to be provided. Unlike intermediate links, which are dynamically extracted from a page and filtered through a pattern you provide, the initial URL has to be exact, so that Obtainium knows where to start from. If the URL of a resource changes every time, for example https://example.org/20240629.json, https://example.org/20240715.json, ..., then it can't be used in Obtainium.
2. The final URL has to be complete
   When text matching fallback is used, Obtainium uses the regular expression pattern (http|ftp|https)://([\w_-]+(?:(?:\.[\w_-]+)+))([\w.,@?^=%&:/~+#-]*[\w@?^=%&/~+#-])?. In the resource being scraped, URLs must be complete, e.g. https://example.org/download/example.apk; "partial" URLs like example.org/download/example.apk or /download/example.apk won't be included by Obtainium.
   This is the limitation I encountered while trying to add configuration for PPSSPP development builds, where all the parts needed are available, but the final URL can't be manually constructed.

For App Cloner's case, neither of the limitations are present. The download links are embedded into JavaScript file that is always at https://appcloner.app/dist/main.js, and the download links are complete. Take one line of main.js for example:

ka(/* ... */, "a", [["class", "app-install-button"], ["href", "https://appcloner.applisto.com/download/AppCloner-2.18.2-24071318.apk"], /* ... */

I'll create a configuration for App Cloner soon, if no surprises appear, you'll be able to install and update App Cloner using Obtainium 👍.

[DwainZwerg]

In principle, I was aware that it was due to static or non-static pages. But I rarely find the static json pages. How do you find them?

[Hamster45105]

In principle, I was aware that it was due to static or non-static pages. But I rarely find the static json pages. How do you find them?

@DwainZwerg You can do this by using the Network tab in your browsers developer tools. If any JSON files are loaded they will appear there.

[LightWayUp]

@nOneCode4u Here is the configuration for App Cloner 🎉.
To add the configuration to Obtainium, you can tap the above link, or wait for changes to be merged and website to be updated, then search for "App Cloner".