AssertionException thrown and Mesh turns invisible when changing Material Offset manually via the Inspector or through SetTextureOffset() on a Mesh with more than one Material

How to reproduce:

1. Open the project “IN-99384_URP“
2. Remove the package Window → Package Manager → Unity Registry → com.unity.render-pipelines.universal
3. Click OK to “Restart” when prompted
4. Install Window → Package Manager → Unity Registry → com.unity.render-pipelines.universal
5. In the Hierarchy click “portal03”
6. In the Inspector expand “portal03_fireSurface (Material)”
7. Type “5” (or any other number) into the Surface Inputs → Offset X-axis
8. Observe the Scene

Expected result: The offset is applied correctly
Actual result: The Mesh disappears from the “portal03” object visually

Reproducible with: 6000.0.38f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a8
Not reproducible with: 2022.3.61f1, 6000.0.37f1
Could not test with: 6000.2.0a9, 6000.2.0a10 (InvalidOperationException thrown but the Mesh is visible in Play Mode, invisible in Scene View)

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:

• The issue also appears when changing the Offset in code using SetTextureOffset(). This can be seen by entering Play Mode instead of changing the Offset manually through the Inspector field
• Issue does not happen in the Windows build