Pokemon Go:Update 0.63.0??

Pokemon Go New Updates Coming This Week:


As the New Server Update is been  came so its time to get  the Client Update for sure this week.....

What are the things in the Server Update :

1)Redeemable codes
We first encountered redeemable codes in our 0.59.1 data mine, detailing how redeemable codes are written. We also know what redeemable codes can reward: Items, Avatar Swag, Candy, Stardust and PokéCoins.
With 0.61.0 we learned a few new things:
  • redeemable codes are tested and ready to release!
  • codes are redeemed via the in game shop
  • there are two or more types of redeemable codes (promotional, etc)
First evidence of testing came from exception messages found in the APK, noting a few errors that the game throws if the redeemable code was already consumed:
promo_enter_code_prompt
promo_enter_code_already_redeemed_response
promo_enter_code_success_response
promo_enter_code_failure_response
passcodeaction
redeem_passcodefeedback_added_xp
We also came across more details on redeemable codes, indicating that this feature is complete and ready to be activated for a future event:


.StorefrontRedeemCategory
.generateCoins
.RedeemNow
.rewardProto
.redeemButton
.placeHolder
.inputText
.redeemPasscodeService
.promo_redeem_button


2)Personal notification inbox

Apart from Redeemable codes, Niantic used this release to introduce the Notification Inbox, a one stop hub for all Notifications submitted by Niantic.
The notification inbox includes the following categories:
  • Marketing
  • Announcement
  • Admin Note
  • Game Event
  • Unset Category
And those notifications can have three different status states:
  • Unread
  • Expiring Soon
  • Immediate
This feature goes hand in hand with the Redeemable codes support, as Niantic needs a way to notify players of upcoming, important and soon-to-expire codes and events. This feature doesn’t look completely done yet, but it’s still a notable addition.

3)PokéStops rewards rewrite

For no apparent reason, the whole code behind PokéStop rewards bubble was rewritten and optimized. We are not sure why this was done, it’s possible it was a required change for other bug fixes.
The code features several animation and sound optimizations, but in essence, it’s still the same behaviour as it was before.

4)Sky rendering changes

There were significant changes to the in game skybox rendering. There is no indication this is connected with the previously leaked sunset animations, but it has potential to move in that direction.
.skyMaterial
.midCloudsMaterial
.farCloudsMaterial
.cloudTexture
.StarTexture
.skyRequest

5)Performance improvements and bug fixes

Without going into technical details, there were numerous performance improvements and bug fixes all across the board. We’ve observed the following:
  • Gyms battles now work without much lag
  • Dodge has been fixed
  • Egg collection dates are now correct
  • App loading time was improved
However, not all players are reporting the same. This is still being researched, but early reports indicate that the game is very buggy on Sony Xperia phones, especially lower end ones.


What are the things on Client Side???

Update 0.63.0 Coming ???

1. Hello gym rework

One of the biggest expectations we have is the inclusion of client side code required for the release of the upcoming gym rework.
Hanke went all out earlier and confirmed that “all new cooperative social gameplay experiences” are coming this Spring. With May coming in a few days, we expect the new 0.63.0 APK to contain a lot, if not all, of the required code base for that.
There is always a possibility that Niantic will miss their earlier estimates and deliver this feature a bit later, but we’re quite confident that this release will include the fabled gym rework.

2. Gym raids are the Gym rework in question

Our next expectation is that the 0.63.0 update will reveal that gym raids are actually the gym rework in question!
The existence of gym raids has leaked earlier in the client app’s network traffic, and as far as we know, at the time of the leak they were available for “dog food testing” purposes. Dog food testing is a principle of software testing where only developers test an upcoming feature, or as the popular terminology says, they “eat their own dog food”.
"gym_removal_notification_toast" "{0} has fought hard and returned!" 
"{0} は "pokemon_hungry_notification_toast" "{0} is hungry!" "{0} はお腹が空いている"
"pokemon_lost_notification_toast" "{0} lost a battle!" "{0} は負けてしまった"
"pokemon_won_notification_toast" "{0} defended the Gym!" "{0} はジムを守った!" 
"nearby_raid_notification_toast" "Nearby raid starting soon!" 
"近くのジムでバ "gym_removal_notification_toast|1" 
"{0} is back after a hard battle!" "{0} が 
"gym_removal_notification_toast|2" 
"{0} was forced off the Gym!" 
"{0} がジムか "pokemon_hungry_notification_toast|1" 
"{0} needs a pick-me-up!" "{0} のお腹が 
"pokemon_hungry_notification_toast|2" 
"{0} wants a berry!" 
"{0} はきのみを欲 "pokemon_lost_notification_toast|1" 
"{0} was defeated in battle!" "{0} は負けて 
"pokemon_lost_notification_toast|2" 
"{0} fainted at the Gym!" "{0} はひんしになっ 
"pokemon_won_notification_toast|1" 
"{0} was victorious in battle!" 
"{0} はバトル "pokemon_won_notification_toast|2" 
"{0} has triumphed over your opponents!"
"nearby_raid_notification_toast|1" "There's a raid about to start near you!"
"nearby_raid_notification_toast|2" "A raid's going to start nearby!" "近くでバ