Search Issue Tracker

Fixed in Unity 2018.3.11f1



Found in


Issue ID




Unable to find a corresponding location while using Partial classes/methods when debugging




Priority: 2Necessary for shipping a final release


Severity: 3Secondary functionality broken

Reproduction steps:

1. Open "Test" project and "SampleScene" scene
2. Open "TestClass.Partial" in VS
3. In Line 9 add a Breakpoint
4. Attach to Unity
5. Enter Playmode
6. Hover over the Breakpoint
7. Notice an error "The breakpoint will not currently be hit. Unable to find a corresponding location"

Expected Result: Debugging works as expected with Partial classes/methods
Actual Result: While debugging, unable to find a corresponding location while using Partial classes/methods

Fixed in: 2019.2.0a9, 2019.1.0b8, 2018.3.11f1

Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2018.3.0f1, 2018.3.0b7, 2018.3.0b4
Did not reproduce on: 2018.3.0b1, 2018.3.0a1, 2017.4.19f1, 2017.3.0a1

Comments (2)

  1. 799da5837578b2129cc7006bbcdb787b?d=mm


    Feb 12, 2019 18:21

    Still in issue in 2018.3.1f1 and it is a regression. Ugh!

  2. 52812772a74d4ea06fe75e51c3ab9bfb?d=mm


    Jan 30, 2019 01:58

    This has been driving me nuts for months. I do use partial classes in my project, but it also happens in ordinary class files, seemingly at random. A whole file will be like this for days or weeks and then suddenly it works again. There's a thread about it here:

All about bugs

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