Further adding this here for more visibility and help, but I reported this issue last night - and was curious on if others were experiencing the same issue?
After performing further troubleshooting because the device is now on Android OS 15, and having the same exact issues, I believe I have found a workaround and or a cause for the crash reports.
My main server is Town Portal, however at the login screen after it authenticates with Bnet, if I chose another server to play on - go to the “new character screen” and back out - then go to the switch server list - and back to Town Portal, I am able to login with no crashing.
So there seems to be some kind of issue on Diablo Immortals authentication end, that is not letting me directly authenticate to the server I need. Is there a login cache stored on your infrastructure that can be temporarily cleared or reset - without losing any progress on my end, or is this just my new login routine until it magically gets fixed.
As soon as I start DI the wait/close buttons appear. At the server selection screen, when I choose wait, 2 or 3 times, it finally loads the character load screen. Sometimes, after hitting wait 3 or 4 times I’m able to log into the game. Other times it never logs into the game.
After logging my character into the game it doesn’t solve anything. I constantly get the wait/close every few seconds until I end up closing it and not playing.
It’s frustrating because I purchased stuff I need to log in for every day to collect. With this issue I haven’t been able to log in the past couple days.
I’m using a Pixel 9 Pro XL running Android 15.
On Reddit people have had same issues with iPhone 15 pro, OnePlus Nord, Motorola…
Same issue. However, this issue causes the right half of the screen to not recognize touch, so you cannot always click the server selector. If it does recognize touch, it just goes to character selection, but game is broken at that point.
As an update, I noticed every time I was having issues with the crashes, my resolution and my android buttons were misplaced when I would alt tab the game.
So, I slapped it back to what I usually use, which is “Full Resolution” because it was randomly set to “High Resolution” instead for some reason.
Since I made this change, the weird alt tab behavior didn’t exist and I have been able to launch and login 4 separate times, without any crashing.
Which makes me think that the crashing was occuring when the application was trying to set what to make the resolution of the game or causing some kind of resource leak or issue when trying to properly scale the application.
Can others here try to check to see if this resolved their issue?
Troubleshooting this issue, I discovered if I go into the developer options and simply toggle off show layout bounds, the problem goes away. It does not survive a reboot though.