Last week was quite a hectic one for the packagers and developers of Open GApps. Google released a new stable branch of Chrome into the Play Store using their own forked ‘Crazy Linker’. At first this was unknown, so when the new Chrome got committed to the repository suddenly different errors started to appear.
So, what happened and what went wrong? An application like Chrome is stored in an APK, which is a kind of ZIP-file. Normally, when preparing an APK to be included on the
/system/ partition of your device, all files that are part of the lib-folder within this APK are extracted and stored separately in a
/lib/-folder next to the APK. The APK itself is stripped from this lib-folder.
But when Chrome started to use this special linker application, this has changed. Suddenly we should not extract everything from
/lib/, but exclude
crazy.libchrome.so from extraction. They have to be kept within the APK in a special non-compressed manner.
So this had to be implemented in the code of the Open GApps scripts, which was done in a quick (and dirty) code fix that had to be ready within a few hours, so that everything would be in place for next day’s release.
In the end, everything worked out, and you as user might not have noticed anything. But for us it were some hectic hours, trying to find the source of the errors and fixing it!
Today we launched our stable releases branch! Check it out at opengapps.org