oSumAtrIX
oSumAtrIX
> Activities and intents are pretty common on Android. All plugins that require interaction need to use them for UI. But they would be abstracted by the plugin API. The...
> The webView library contains an activity class, which is final and the user does not directly interact with it. The library needs to be implementation instead of compileOnly because...
> By "internal", do you mean completely inaccessible to plugins? Yes. I was thinking it was an internal only API so we would provide wrappers to that internal function. `webView`...
> How would cases where interaction is only required conditionally be handled? I don't quite get the interaction part. Is this just metadata provided by the plugin for ReVanced Manager...
### Offtopic On second thought, having a launch and result function is not really necessary. It is readable and allows for flexible transformation grouped by scope though. The intent scope...
> It is part of Ushies design. Also, if there is no prompt the user might be thrown into a bunch of activities for downloaders they don't want to use...
> using the provided Context Is it necessary to pass the entire context down? Context for the purpose of launching intents can already be done internally via a public facing...
https://github.com/ReVanced/revanced-patcher/commit/5ec9f390e1d48d1f40581b9f9caa3faa7f162b55 This should solve the issue
Because it is not an OOM error
There's a linear memory leak at compile time of DEX if I recall correctly. Dexlib lazily reads classes, however with every class written it needs to be read fully, thus...