![]() An image was included for this mod, but the image is completely blank. This is probably because Niantic is getting tired of teardowns revealing information before they can, so they keep the descriptions blank till such item is ready to launch. In the case of EXTRA_SHIELD, the value for the human readable string was null along with a null description. Usually when items are in development (like Capsules), their entry in this file includes a human readable name and a description. This time I was quite surprised when I saw a new item named “EXTRA_SHIELD”. There are a few files I watch when looking for new items. This seemed like a version to just update all the dependencies on. ![]() ![]() On top of a new obfuscator version, new versions of the internal Google Play Services, JSON Parser and libGDX have been included. This can be seen overall via the diff report of 1.64.0 compared to 1.65.0.ħ109 files changed, 236,284 insertions(+), 202,269 deletions(-) Directories shifted locations and even Unicode variables were added to just relocate data for the purpose of obfuscation. We are looking at a newer iteration of obfuscation and a bit more effort into hiding whats in the APK. As versions have come out, my tools have become “smarter” at handling this.ġ.65.0 changed all of that. This is because Proguard (the obfuscator) used for Ingress shifts the naming of variables among the source files which causes quite a lot of false alarms in the diff reports. Usually a new version has around 300-1200 files changed. ![]() You would be surprised at the amount of changes that go un-announced or simply hide in the APK for an upcoming release. For those new to Teardowns, we simply compare the previous release (1.64.0) to the current one (1.65.0) and note the differences. Welcome back to another Ingress teardown. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |