Steps to reproduce:
1. Open the attached “OpaqueMSAAShaderBug” project
2. Build And Run the project on the device
3. Observe the device’s screen

Expected result: The “OpaqueCube” GameObject on the right side of the “Cube” GameObject is visible
Actual result: The “OpaqueCube” GameObject is not visible

Reproducible with: 2022.2.0a16, 2022.3.20f1, 2023.2.10f1, 2023.3.0b7
Not reproducible with: 2021.3.34f1, 2022.2.0a15

Testing environment: macOS Sonoma 14.2.1 (Intel)
Not reproducible on: No other environment tested

Reproducible with devices:
VLNQA00526 - Samsung Galaxy A12 (SM-A125F), CPU: Mediatek MT6765 Helio P35 (12nm), GPU: PowerVR Rogue GE8320, OS: 12
Vivo Y16, CPU: MediaTek Helio P3 (by user)

Not reproducible with devices:
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS

Notes:
- Not reproducible with iOS and Standalone
- The GameObject is visible when Alpha Clipping of “OpaqueMaterial” of “OpaqueCube” GameObject is disabled
- The GameObject is visible when Anti Aliasing (MSAA) in URP-Balanced asset is disabled
- “IMGSRV SetupLinkedFragmentShader: Failed to link fragment shader” and “IMGSRV DrawElements: ValidateState() failed” errors are spammed in the logcat with reproducible devices