Clash Royale Dev Tracker

We've released an Optional Update that contains a list of fixes that will resolve a lot of issues and improve game performance on various devices. Thank you for sending us bug reports!

The Optional Update can be found in your relevant app store - please make sure to update to enjoy the best possible experience with Clash Royale!

Patch Notes:

• Fixed a number of Android device crashes
• Shop no longer crashes or freezes when tapped
• Fixed the issue where the game would crash at 100% loading after playing audio
• Watching a replay from before the update doesn't cause the game to crash
• Crown Chest unlock timer displays correctly on the home screen
• Chest queue notification now delivered correctly
• Fixed a black line appearing under a player's name in the Clan chat messages
• All app stores Terms of Service now display correctly
• Pass Royale name color is now displayed correctly...

this is a very cool idea - i'd love to gift some of my friends back home pass royale!

have put it on our wishlist/ideas board.

thanks!

fixes are in my stickied comment here

Hey there! Here's how this happened:

While reworking Quests, we decided to re-write the lines into a simpler syntax. For example:

"Play cards that cost 6 Elixir or more 30 times" -> "Play 30 cards that cost 6 or more Elixir". The latter reads more naturally. When we got to "2 or less Elixir" string, we decided to rewrite it as "1 or 2 Elixir". In the Quests data, that's a simple change to make Min_Elixir = 1 (it was null before). Each Quest has its own min/max elixir setting, which is how we added the new Play 3-Cost, Play 4-Cost, etc Quests. Min and Max is just set to that number.

When the update goes live, the strings updated but the data of each Quest was saved from the moment you got the quest. So even though the conditions of new Quests were updated, any existing ones used their stored data. Since the Quests had null for min_elixir, the updated string didn't have a number to reference and that's why it displays as the variable name.

This is also...

☝️ this guy ^almost gets it 😜

we're trying to squeeze a few more bug fixes into this maintenance so it's coming a bit later than originally stated

Nice try, Supercell... 😒

we can perform a maintenance anytime we are ready, without any external approval.

but for an optional update we need to have it sent off to various app stores and approved by those app stores before we can make it available to our players, which can slow us down significantly when it comes to fixes.

some fixes cannot be performed in a maintenance, and therefore have to go in an update.

i hope that helps you understand the situation a bit better

i'm sorry - i understand it's affecting your gameplay - but as we haven't completed all the work for the optional update yet, i have no solid ETA to give other than this week.