lol I wrote 19 august xD I wanted to say 29* (sorry) the same day of the update for mobile version (at 22pm in my case). So as the problem exist in all devices should not be related to the update really, is just a coincidance... despite all as said should be solved in the next hours
