zip - Android expansion (obb) patch file version number -
i have uploaded application play store huge expansion (obb) file. everything's working fine, no problem that. have upload small update expansion file. want use patch expansion file because don't want force users download big main expansion file again. in theory it's seems easy task.
from developer page:
// zipresourcefile representing merger of both main , patch files zipresourcefile expansionfile = apkexpansionsupport.getapkexpansionzipfile(appcontext, mainversion, patchversion);`
i have used in form:
zipresourcefile expansionfile = apkexpansionsupport.getapkexpansionzipfile(appcontext, 14, 0);'
with no patch file , no problem.
but if try modify code, got problems.
my current version 19, still use main expansion file 14 version. when tested app used 14 version number of patch file (patch.14.com.exaple), copied patch file directly phone , used code:
zipresourcefile expansionfile = apkexpansionsupport.getapkexpansionzipfile(appcontext, 14, 14);
everything's fine, app find updated files in zipresourcefile it's true, "zipresourcefile representing merger of both main , patch files"...
i've tried upload modified apk , patch file in developer console after upload realised changed patch file's name current version number: patch.19.com.exaple , can't change 14. cancel upload , modified code:
zipresourcefile expansionfile = apkexpansionsupport.getapkexpansionzipfile(appcontext, 14, 19);
but after app didn't find updated files - seems it's using main file. i've tried test on phone, changing file names of obb files , code in app, , found, "merging" working if version numbers same. in case whole "main , patch obb files" completly useless (at least in context of apkexpansionsupport.getapkexpansionzipfile) because can't upload patch file later version number of earlier release...
so question is: how can zipresourcefile "representing merger of both main , patch files" if version numbers different in 2 filenames?
Comments
Post a Comment