Search Issue Tracker

Active

Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X

Votes

0

Found in

2021.3.51f1

2022.3.61f1

6000.0.48f1

6000.1.1f1

6000.2.0a10

Issue ID

UUM-103999

Regression

No

Full stack trace is always printed when an exception occurs in an IL2CPP build

-

How to reproduce:
1. Open the attached “IN-97878” project
2. Select “File → Build And Run”
3. Observe the Player once the build is completed

Expected result: The displayed stack trace in the Player window is short (~4 lines)
Actual result: The full stack trace is displayed in the Player window (~15 lines)

Reproducible in: 2021.3.51f1, 2022.1.0a1, 2022.3.61f1 (e6a1f07378cd), 6000.0.48f1, 6000.1.1f1, 6000.2.0a10

Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested

Notes:
- The stack trace can also be seen in the Player log. Information about where to find it is found here: [https://docs.unity3d.com/6000.0/Documentation/Manual/log-files.html|https://docs.unity3d.com/6000.0/Documentation/Manual/log-files.html|smart-link]
- Not reproducible with Mono scripting backend
- Not reproducible in the Editor

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.