Attention Android Users!
Dec. 19th, 2019 03:02 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
IF YOU HAVEN'T UPDATED YET, PLEASE DON'T! (yet.)
There are issues with the Start button in Fortresses giving an error when players tap it to enter a Wizarding Challenge.
This is affecting Android players on the new app version 2.8.0. If you are on 2.7.0, the issue will not affect you.
THIS AFFECTS EVERYONE: For the time being, they've turned off the Start button for the Wizarding Challenges and set the timer back to 20 seconds while they work on a fix, but until then, it might be best for Android users to hang on to the less buggy version. (Last I checked, 2.8.0 hadn't appeared in my app store yet anyway... 😐)
In general, if you get errors like this, do not tap ok. Force quit and restart the app and you are often able to get back into the challenge. It's not guaranteed though. There's also been the occasional problem with the start feature in 2.7.0 due to clicking on it as soon as it appears. Players have to wait at least a few seconds after the start button appears for it to work properly. If you don't, you may well lose Runestones because of it.
I'll keep you posted...
There are issues with the Start button in Fortresses giving an error when players tap it to enter a Wizarding Challenge.
This is affecting Android players on the new app version 2.8.0. If you are on 2.7.0, the issue will not affect you.
THIS AFFECTS EVERYONE: For the time being, they've turned off the Start button for the Wizarding Challenges and set the timer back to 20 seconds while they work on a fix, but until then, it might be best for Android users to hang on to the less buggy version. (Last I checked, 2.8.0 hadn't appeared in my app store yet anyway... 😐)
In general, if you get errors like this, do not tap ok. Force quit and restart the app and you are often able to get back into the challenge. It's not guaranteed though. There's also been the occasional problem with the start feature in 2.7.0 due to clicking on it as soon as it appears. Players have to wait at least a few seconds after the start button appears for it to work properly. If you don't, you may well lose Runestones because of it.
I'll keep you posted...
no subject
Date: 2019-12-19 02:24 am (UTC)Oops already updated. It's always lagged on me anyway.
no subject
Date: 2019-12-19 03:05 am (UTC)They have had the worst luck with that start button feature. I've lost count how many times they announced they'd fixed it, only to have them realise they hadn't and turn it off again.