Regular screen freezes since iOS 26.2

Bug Report
1

In addition to a description of the bug you are reporting, please provide:

  • Device Type: iPhone
  • Device Model: 17 Pro Max
  • Device Operating System: 26.2
  • Warcraft Rumble App Version: 15.52.0

Game has been increasingly unstable since iOS 26, but now ‘freezes’ much more frequently after updating to iOS 26.2. Often, a match will load and then all animations will freeze - the entire phone becomes unresponsive for a few seconds. After a while, I can swipe up to bring up the app switcher. If I try to go back to Rumble, the screen shows flashing, repeat animations continuously. At this point, I have to close Rumble and re-open in order to clear the ‘freeze’

2 Likes
2

I’ve got the same issue.

iPhone 17 Pro. iOS 26.2.

This game should fly on these phones.

1 Like
3

Same issue. It has gotten worse recently. iPhone 17 Pro. IOS 26.2

4

Almost unplayable by mobile at this point. (At least the PC version remains stable.)

5

Same here, almost unplayable.

iPhone 17 Pro. IOS 26.2

6

Same here! Daily I have to restart the app to continue playing.

7

Same phone, same version, same problem! Can we please get this fixed? Been going on way too long for a popular phone

8

No freezes on PC, but performance is very unstable and poor since the latest Unity updates. Looking through the logs, I have identified the following critical engine errors:

Main Thread Stalls:

AssetBundle.Unload was called while the asset bundle had an async load operation in progress. The main thread will wait...

Garbage Collection Spikes:

Unloading 127610 unused Assets... Total: 146.029600 ms

Missing VFX Assets:

No mesh data available for mesh pSphere1 on particle system VancleefShip_Missile_TrailGeo

Initialization Errors:

Unable to access the TierRegistry. Was GetCurrentDeviceTier called before LoginSession was created?

UI Scaling Loop:

ERROR: Cannot Match both Vertical & Horizontal.

9

After updating to iOS 26.2.1 and playing the game for 2 days now, the game has not frozen on me yet.

10

Looks like that wasn’t the fix. Had it freeze on me again about 2 minutes ago

11

Same issue here. My general thought was that some other app is interfering and Rumble does not have the proper error handling to avoid the freeze. I was thinking something like Oura ring or MyHonda app.

I found one of the freeze logs in iOS and asked Claude about it. This was the details it gave.

What the Log Is

File type: gpuEvent (bug_type 284) — this is a GPU hang event, not a traditional app crash. The GPU became completely unresponsive, which is why the game just freezes rather than crashing with an error message.

  • When: June 12, 2026 at 11:12 AM CDT

  • OS: iPhone OS 26.5.1 (23F81)

  • Root cause: restart_reason_desc: "blocked by IOFence"

The Actual Problem: IOFence Deadlock

An IOFence is a GPU synchronization primitive — essentially a gate that coordinates when shared GPU memory (called an IOSurface) can be read vs. written. Think of it like a read/write lock for graphics buffers.

The log shows a deadlock on IOSurface #220 between two GPU contexts:

Side Accelerator Direction Status
Current queue Accelerator 0 Write (1) Holding the surface, never releasing
Waiting queue Accelerator 2 Read (2) Waiting forever for the write to finish

Accelerator 0 holds a write lock and never signals it’s done. Accelerator 2 is blocked waiting to read. Neither can proceed — the GPU deadlocks, and the entire game freezes.

The field guilty_dm: 1 further flags the display manager as the responsible component in this hang chain.

Why It Seems Random

IOFence deadlocks are timing-dependent. The deadlock only occurs when two GPU command streams reach the contention point at the same moment. That window could be triggered by:

  • A specific in-game effect or animation (particle burst, spell, transition)

  • The system compositor and the game’s Metal renderer racing on a framebuffer

  • Device thermal/performance state changes (note fw_power_substate: 4 — a non-baseline power state)

This explains why you can’t find a consistent pattern — the trigger could be nearly anything visually, but the cause is always the same underlying race condition.