How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Mobile Game Flickering Between Portrait and Landscape on Launch

Q: What causes a mobile game flickering between portrait and landscape on launch?

The activity or view is created in the device's current orientation and the game's preferred orientation is applied only afterward, so the first frame flickers in the wrong layout.

Quick answer: Declare the fixed orientation in the platform manifest or Info.plist so the OS creates the window in the correct orientation from the start.

Launching your landscape game in portrait shows a momentary squished frame before it rotates. The orientation lock is applied at runtime after the window exists. Set it in the manifest so the first surface is already correct.

How to fix it

1. Lock in the manifest

On Android set android:screenOrientation for the activity; on iOS set the supported orientations in Info.plist, so the OS never creates the window in the wrong orientation.

2. Avoid runtime-only locking

Setting orientation only from script runs after the first layout, which is exactly what produces the flicker; the platform declaration prevents the wrong initial frame.

3. Match the splash orientation

Configure your launch/splash screen for the same orientation so there is no rotation between the OS splash and your first rendered frame.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every mobile error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.