[Android] Cannot Access Profile or Alliance - Frozen

Device and Version: Motorola Z4

Device Operating System: Android, 10, Build QDF30.130-42-1

Mobile Carrier: Verizon

Cellular or WiFi: Both

Game Version Installed: 26.1.1

Game Mode: This issue occurs in all Game Modes.

Champions Affected: No Champions affected. Not applicable to issue.

Active Boosts: No boosts active. Not applicable to issue.

Description of the Issue: Each time I attempt to access my profile, my alliance page or launch AW/AQ, the screen dims and the entire application freezes. I must close it and reopen to regain any functions. I have toggled Wi-Fi/airplane mode. I have uninstalled and reinstalled the app to no avail. This is occurring every time I attempt to access. The problem has been happening since April 13th.

Screenshot or Video:

Comments

Graewood

This has also been happening for me when I press on the AW screen in particular.
Everything freezes, I have to close the game and re-open.

Running a Samsung Galaxy S8, latest version of android. Wifi and network data.

Lots of issues since the Baron's War change on wednesday!

mgj0630

This is happening to me as well, though slightly different, as the only thing I cannot access is the Alliance tab. Whether I click Alliance from the drop down menu at the top, or select the Help icon from the bottom of the home screen, the result is the same as the screenshot @riddleme33 posted.

I first noticed it the morning of Wednesday, April 16th. Coincidental timing after server maintenance on April 15th.

I posted a thread in the general section just to ask if others were also experiencing this, but only received one reply to say no.

https://forums.playcontestofchampions.com/en/discussion/191843/alliance-tab-broken#latest

I have two devices, a tablet with Android 6.0 and a phone with Android 10.

I have force stopped, cleared cache, and rebooted each device to no avail. The only thing I haven't done is uninstall/reinstall, but as the OP points out having done this without resolving the issue, I don't see any reason to do the same.

If anyone at Kabam could look at this, I'm more than happy to try and collect additional data to help debug if the staff isn't able to reproduce the issue.

Thanks in advance.