I have a project with a very large cordova plugin (about 200MB). This plugin by itself adds about 110MB to the final APK that I build. Is there any way I can add this plugin to an APK expansion file?
There is a Cordova plugin to handle expansion files:
Problem will be that this is made for content, not really plugins. What does take so much space in this plugin? You probably will have to extract some things as I don’t really see a way to take the whole plugin (In the APK this isn’t this neat folder of stuff, but things all over the place most of the time).
Thanks for the reply.
That’s the plugin I had looked into before posting. The problem I’m having is with a pretty large asset in a custom plugin that was built for my organization (over 90MB). Fortunately, I researched the developer’s comments, and it appears that this data file will automatically be downloaded when the plugin starts for the first time if it cannot be found locally. I haven’t test this mechanism in months, but if it works, it would solve my problem since the absence of the data file would drop my APK below 100MB. Thanks again for your time.
Even if it doesn’t work, this Cordova plugin I posted seems to be perfect for assets - so maybe you just have to make your current plugin a bit more fault tolerant while the expansion isn’t there yet.
Wish I could, but I didn’t write the problematic plugin we’re using in our app. It references native android code that I don’t have the source for. The android code’s assets are the data hog.
1 Like