After updating I tested a fight in the Abyss and Labyrinth of legends. I was hoping the freezing of the screen for a couple of seconds before the fight would have been solved. Since it was mentioned in the release notes. But sadly the problem was still there. I play on a Xiaomi Note 8 pro. I experience this issue in the AOL, LOL and AQ map 5 (map 2 didn`t give any problems weirdly), the problem does not happen anywhere else as far as I know. The phone runs on adroid version 10. And as mentioned I updated the game to the latest patch. Since I want to attempt my initial abyss run soon I would really appreciate it if you guys can look into this.
After updating I tested a fight in the Abyss and Labyrinth of legends. I was hoping the freezing of the screen for a couple of seconds before the fight would have been solved. Since it was mentioned in the release notes. But sadly the problem was still there. I play on a Xiaomi Note 8 pro. I experience this issue in the AOL, LOL and AQ map 5 (map 2 didn`t give any problems weirdly), the problem does not happen anywhere else as far as I know. The phone runs on adroid version 10. And as mentioned I updated the game to the latest patch. Since I want to attempt my initial abyss run soon I would really appreciate it if you guys can look into this.
I'm kinda tired now ....why is it not getting fixed
Happens to me as well in Abyss, LOL and AQ. It's a shame that it is not solved after nearly 2 months. All my saved revives will be gone soon so this bug sucks heavy for me.
Took me 45minutes to clear one lane in 6.1.1 because of constant connection problems on rock solid 4g. Click fight, times out. Reload game, times out trying to load. Get in game, times out trying to load map. Reload game, times out after clicking fight button. Over and over and over.
I have been playing game for years on Samsung Galaxy Tab A. Game often freezes in the middle of a fight and i have had to shut down game and restart, often losing half my life. Since latest update, I can sometimes fight one fight, or sometimes not even start the first fight, before game freezes. Not always consistent where.....sometimes blank screen, sometimes with wheel spinning.
Ok, i noticed this: When I click "fight" on the pre-fight screen: If 0 ≤ timer ≤ 30: After 30-40 seconds, I get sent in the map without fighting. I lose 50% HP.
If 35 ≤ timer ≤ 45: After 30-40 seconds, I face the infinite loading screen, forcing me to restart the app (and lose 50% HP anyway)
So for me (and for some other players) the pre-fight timer is 15 seconds. Considering that 2-3 second are lost if you want to change the attacker, you have too less time to click "fight".
Now, this bug is here since July 2020. I haven't read anything about a possible fix. I hope we will receive a good compensation for such stuff.
Same things been happening to me for up to 6-8 months now and I'm tired of sending tickets to complain and also spending time and money to get units to heal back up. Anytime I click the fight button in AQ, it stays loading endlessly until I manually restart the game myself and boom I've lost half the health of my champions. Please do something about this cause I'm on the verge of quitting as I'm tired of this bug ruining AQ for me. @Kabam Zibiit@Kabam Porthos@Kabam Miike@Kabam Porthos
DEVICE DETAILS In-game name : Bercouli001 Device name: Tecno Camon 12 Model : Tecno CC7 Android version : 9 Game version: 29.1.0
The video shows my Loading loop. Unfortunately, I clicked fight when there were only 43 seconds left.... Too close to the end. I would like to reiterate this: I can start to click "fight" when the timer is at 57. So I only used 14 seconds taking the revive and the potion. I was lost in thought and I clicked "fight". It looks like that my real pre-fight timer is almost 15 seconds. I demand for compensation, since I spent (now wasted) potions
Thank you for the videos! This helps immensely in sharing information with the rest of the team.
This bug was detected 6 months ago and nothing happend. What is the status of the developers? I can't play LOL or AOL and AQ is very time consuming with this bug.
Labyrinth still doesn't work for me, as soon as I click fight the game crashes... I wanted to try out she hulk in labyrinth cuz rol ai is too passive, but it has been more than a month now without any acknowledgement or fix. Ffs.
Comments
I play on a Xiaomi Note 8 pro. I experience this issue in the AOL, LOL and AQ map 5 (map 2 didn`t give any problems weirdly), the problem does not happen anywhere else as far as I know. The phone runs on adroid version 10. And as mentioned I updated the game to the latest patch.
Since I want to attempt my initial abyss run soon I would really appreciate it if you guys can look into this.
I recorded a video of the first abyss fight for reference.
The result is the same, I have to restart the game, losing half my health.
When I click "fight" on the pre-fight screen:
If 0 ≤ timer ≤ 30:
After 30-40 seconds, I get sent in the
map without fighting. I lose 50% HP.
If 35 ≤ timer ≤ 45:
After 30-40 seconds, I face the infinite
loading screen, forcing me to restart the
app (and lose 50% HP anyway)
So for me (and for some other players) the pre-fight timer is 15 seconds. Considering that 2-3 second are lost if you want to change the attacker, you have too less time to click "fight".
Now, this bug is here since July 2020. I haven't read anything about a possible fix. I hope we will receive a good compensation for such stuff.
DEVICE DETAILS
In-game name : Bercouli001
Device name: Tecno Camon 12
Model : Tecno CC7
Android version : 9
Game version: 29.1.0
The video shows my Loading loop. Unfortunately, I clicked fight when there were only 43 seconds left.... Too close to the end. I would like to reiterate this: I can start to click "fight" when the timer is at 57. So I only used 14 seconds taking the revive and the potion. I was lost in thought and I clicked "fight". It looks like that my real pre-fight timer is almost 15 seconds. I demand for compensation, since I spent (now wasted) potions
They. Don't. Care.
I can't play LOL or AOL and AQ is very time consuming with this bug.
@Kabam Zibiit @Kabam Porthos @Kabam Miike @Kabam Porthos