Search Issue Tracker
Fixed in Unity 2018.3.11f1
Votes
14
Found in
2018.3.0f2
Issue ID
1118285
Regression
Yes
Unable to find a corresponding location while using Partial classes/methods when debugging
Reproduction steps:
1. Open "Test Project.zip" 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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Slow editor shutdown when baking with progressive lightmapper
- Clicking on cloud icon in "In the Cloud" section, instead of opening Unity Version selector it opens save project location Popup
- ShaderGraph ColorMask material on RenderTexture is transparent while in Game View opaque
- [MacOS] Windows that are unattached are hidden behind Editor when the Editor Window is focused
- Some ParticleSystems use the wrong texture when several of them are being rendered with different Textures
stonstad
Feb 12, 2019 18:21
Still in issue in 2018.3.1f1 and it is a regression. Ugh!
DigitalGod
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: https://forum.unity.com/threads/the-breakpoint-will-not-currently-be-hit-unable-to-find-a-corresponding-location.465034/