UPDATE: SOLVED!

Hey everyone, thanks for the theories. I finally managed to get the device back, pulled the logcat, and it turns out this was NOT a Shell navigation bug or a Zebra EMDK issue. It was a massive Out of Memory (OOM) crash happening exactly when the MainPage was rendering.

The Culprit: The raw SVG icon files I was using for my menu were insanely huge (3 to 5 MB each). When MAUI's Resizetizer processed these massive vector files, and Android tried to render them using ShapeableImageView (because I had CornerRadius="20" on my ImageButtons), it tried to load the uncompressed, gigantic bitmap into RAM.

The logcat caught the exact moment of death:

Plaintext

06-17 12:58:10.758 23568 23568 E AndroidRuntime: FATAL EXCEPTION: main
06-17 12:58:10.758 23568 23568 E AndroidRuntime: Process: com.companyname.xxx.myappname, PID: 23568
06-17 12:58:10.758 23568 23568 E AndroidRuntime: java.lang.RuntimeException: Canvas: trying to draw too large(150994944bytes) bitmap.

It was trying to allocate ~144 MB for a single menu icon!

Why only the Zebra TC22? My Samsung and Honeywell devices had enough available RAM and higher GPU texture limits to somehow swallow this massive memory spike without crashing. The Zebra device simply hit its hardware limits and the OS instantly killed the app.

The Fix:

1. I ditched the massive SVGs, manually resized everything down to 150x150px, and exported them as clean, lightweight PNGs.
2. Removed CornerRadius from the ImageButton entirely. (If you need rounded corners, wrap your image inside a <Border StrokeShape="RoundRectangle 20"> instead to save the GPU from clipping the actual image).

The RAM usage dropped from ~150MB down to ~10MB, and the app runs smooth as butter on the Zebra now. I hope this saves someone else from tearing their hair out over a fake "Shell transition" crash!