You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #639, Google Drive links were discussed. In that issue, I mentioned a hypothetical in which a webpage has a link to a Google Drive download, and another user recommended using an alternate link that immediately provides the file as a direct apk link. These two methods are entirely incompatible, but a regex replacement could bridge the gap, since the urls are totally predictable and would use the same ID.
The only alternative I can think of for such a situation is using the direct download URL, which isn't viable in situations where the link might change between versions.
Admittedly, this is not high priority in any way. Regex replacements can be super useful, but I can't really think of any uses in Obtanium beyond this hypothetical.
The text was updated successfully, but these errors were encountered:
I think replacement regex can also be usefull for version.
I have the case with Breezy Weather. The version push by github is v5.1.8 but my os give 5.1.8_froid. I allready extract 5.1.8 but is still block with the "_fdroid" string.
In #639, Google Drive links were discussed. In that issue, I mentioned a hypothetical in which a webpage has a link to a Google Drive download, and another user recommended using an alternate link that immediately provides the file as a direct apk link. These two methods are entirely incompatible, but a regex replacement could bridge the gap, since the urls are totally predictable and would use the same ID.
The only alternative I can think of for such a situation is using the direct download URL, which isn't viable in situations where the link might change between versions.
Admittedly, this is not high priority in any way. Regex replacements can be super useful, but I can't really think of any uses in Obtanium beyond this hypothetical.
The text was updated successfully, but these errors were encountered: