Pokemon GO 0.83.1 update data mine: major bug fixes, but no Gen 3

Posted in

Trainers,

our data mine of the new 0.83.1 Pokemon GO update is now complete! Although this update does not contain any new info in regards to Generation III or abilities, it is still a very important bug fixing update. Plus, we’ve got some new code dealing with the upcoming battle parties feature.

Here’s what’s new (according to the official change log):

  • Added support and made optimizations for the iPhone X screen resolution.
  • Removed support for devices running iOS 8.
  • Resolved a bug causing error banners to remain visible until the app is restarted.
  • Resolved a bug that prevented Trainers from powering up Pokémon to their max CP.
  • Improved load times when you open the app.
  • Various bug fixes and performance updates.

And here’s what we’ve found in our data mine.

You are able to power up Pokemon to full level 40

No more level 39.5, no more half level cap madness. You can power up your Pokemon all the way to Pokemon level 40, unlocked once your each Trainer Level 38.

Changes to asset bundle loading

A number of internal mechanisms has been updated and optimized to provide better asset loading inside the app. This includes tracking loaded and unloaded bundles, releasing memory more quickly and faster recovering from a bundle error.

.AssetBundleStatus
.UNLOADED
.LOADING
.LOADED
.IAssetBundleLoadHandler
.LoadBundle
.UnloadBundle

Blacklist optimizations

The code behind the recent blacklisting measure has been changed when compared to 0.81.1 and now features a new “Device Banned” UI. This is an existing check, but now has a new UI screen to accompany it.

.DeviceBanned
.OnDeviceBanned
.blacklistedApps
.OnBlacklistedAppDetected
.bannedPlayerLockoutGuiPrefab
.deviceUnauthorized

Logs, logs everywhere!

Niantic’s shared platform infrastructure continues to evolve, bringing more stability and debugging functionality to their entire product suite.

This time we’re observing an increase in the number of logged events, enabling the development team to discover potential issues and to reproduce the existing ones faster.

Pokedex and inventory caching, memory management and forced loads

Continuing on the above mentioned performance and bug fixing updates, a new layer of caching was introduced, targeting the Pokedex screen.

.set_InventoryCache
.pokedexCache
.get_EnableLocalDiskCaching
.set_EnableLocalDiskCaching

In addition, the app will now manage memory more aggressively and force loading new Pokemon when it deems required. We haven’t measured the actual performance impact yet.

Battle parties max numbers!

Niantic is continuing to work on the Battle Party feature, but no indication has been given on when it will be released.

In this release we’ve observed additional code for handling the maximum number of Battle Parties you are allowed to create.

.get_MaxNumberLocalBattleParties
.set_MaxNumberLocalBattleParties
.MaxNumberLocalBattlePartiesFieldNumber
.maxNumberLocalBattleParties_
.MaxNumberLocalBattleParties

And that’s it for this release, we’re still investigating the APK for image asset changes and new animations. If we find something we’ll report soon.

Author & tags

Tags
Zeroghan
Zeroghanhttps://pokemongohub.net/
Zeroghan started the Hub in July 2016 and hasn't had much sleep since. A lover of all things Pokémon, web development, and writing.

Further reading

Popular today

Latest articles

Support us

Buy GO Hub merch

Get your very own GO Hub t-shirt, mug, or tote.