Replies: 4 comments 2 replies
-
These are Runtime Resource Overlays. They have nothing inside but just a bunch of resources. The reason to use Premade APKs is to reduce the time of building overlays. There is ofcourse alternative way to not use premade APKs, but this is the only solution I found that's the fastest and works on every rom without any hassle. The source can be made public ofcourse, it's currently in my private repo which is very messy rn. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the swift answer, @Mahmud0808 – and yes, that's basically what I guessed already. May I suggest to add a note on that to the description or at least the Readme, for transparency? And yes, please see if you can make the source of the embedded APKs available openly as well. Feel encouraged to take this as motivation for "cleaning some mess" 🙈 |
Beta Was this translation helpful? Give feedback.
-
Source can be found Here Note is added in assets/PremadeOverlays/cheatsheet file. |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot! Mind adding a pointer to the app description as well? Guess it could go as a 4th point into the disclaimer, like <li>Note: PremadeOverlays are used as embedded APKs to reduce the overlay compilation time. For details, please <a href='https://github.com/Mahmud0808/Iconify/blob/beta/app/src/main/assets/PremadeOverlays/cheatsheet'>see here</a>.</li> |
Beta Was this translation helpful? Give feedback.
-
One of my scanners just reported "embedded APKs" (a new check recently added) with your latest release – and indeed there are quite some (68) APKs inside the APK. I've checked the repo, and there they are as APKs inside assets. There seems no danger with these here in this case, but it still raises some questions:
No offense meant at all – just seeking clarification: if an app comes with "root powers", some extra caution cannot hurt, right? So thanks in advance for any "enlightenment" you can give 😃
Beta Was this translation helpful? Give feedback.
All reactions