Back gesture/button closes the app after returning from background when "Run In Background" and "Predictive Back Support" are enabled
Linked bug report
UUM-159613: Back gesture/button closes the app after returning from background when "Run In Background" and "Predictive Back Support" are enabled

How to reproduce: 1. Create and open a new project 2. Navigate to Project Settings, Player tab (Edit > Project Settings > Player) 3. Toggle on Predictive Back Support (Other Settings) 4. Toggle on Run Without Focus (Resolution and Presentation) 5. Build and Run for Android 6. On the device tap or gesture the back action 7. Notice the app doesn’t go to background or close 8. Put the app in fore…

Retrieved 2026-11-10
AndroidKnown issueCautionUUM-159613
"contains a TextureImporter object at version 4, below the supported minimum (10)" warnings are thrown when creating a project from the Multiplayer Third Person Gameplay template
Linked bug report
UUM-156317: "contains a TextureImporter object at version 4, below the supported minimum (10)" warnings are thrown when creating a project from the Multiplayer Third Person Gameplay template

How to reproduce: 1. Create a new project from the "Multiplayer Third person gameplay" template (1.0.9) 2. Observe the Console Expected results: No warnings are thrown on first open Actual results: About 155 "Serialized file "<path>.meta" contains a <Importer> object at version N, below the supported minimum (M). Open and re-save the file to upgrade." warnings are thrown, for 150 template asse…

Retrieved 2026-11-11
Multiplayer FPS/Third Person TemplatesKnown issueCautionUUM-156317
Compilation errors are thrown when creating a project from the "Multiplayer Third Person Gameplay" template after Netcode for GameObjects is upgraded to 3.0.0
Multiplayer FPS/Third Person TemplatesKnown issueCautionUUM-156276
First Person Multiplayer Template does not compile and prompts entering Safe mode on launch due to obsolete code being used
Multiplayer FPS/Third Person TemplatesKnown issueCautionUUM-156433
AssetBundle MonoBehaviour shows as missing script in standalone Player when its assembly is loaded at runtime with Assembly.Load
Linked bug report
UUM-159333: AssetBundle MonoBehaviour shows as missing script in standalone Player when its assembly is loaded at runtime with Assembly.Load

How to reproduce: Open the attached "IN-152532" project Open Build Settings and switch the platform to Standalone (Windows or macOS) Build and run the "ReproScene" scene as a standalone Player Observe the logs of the Player Actual result: The MonoBehaviour from the AssetBundle does not bind to the script of the assembly loaded at runtime, so the component shows as a missing script Expected res…

Retrieved 2026-11-11
Scripting RuntimeKnown issueCautionUUM-159333
[CoreCLR] User frames are missing from Debug.Log stack traces and uncaught exceptions in Start()/Update() have an empty stack trace
Scripting RuntimeKnown issueCautionUUM-159945
RenderPass related Android errors are logged in Logcat and Console when physically rotating the device
Linked bug report
UUM-157974: RenderPass related Android errors are logged in Logcat and Console when physically rotating the device

How to reproduce: 1. Open the attached ‘IN-154071.zip” Project 2. Turn on Development Build and Script Debugging settings (File → Build Profiles ) 3. Build and Run on Android 4. Rotate the Device while the Player is running 5. Observe the Development Console and or Logcat Actual result: RenderPass related errors - “The dimensions or sample count of attachment don’t match RenderPass…” Expected …

Retrieved 2026-11-10
SRP FoundationKnown issueCautionAndroidUUM-157974

Pick your Unity version

Unity Releases compares releases against the version your project is on. Picking it now keeps Compare versions focused on what changes between where you are and where you might be going.