Unity Issue Tracker - Unable to find a corresponding location while using Partial classes/methods when debugging

Fix In Review for 2020.1

Fixed in 2018.3, 2019.1

Fix In Review for 2019.3

Votes

15

Found in

2017.4.11f1

2018.3.0f2

2018.4.4f1

2019.2.0a1

2019.2.0b7

2019.3.0a7

2020.1.0a1

Issue ID

1118285

Regression

Yes

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

Mono

Jan 18, 2019

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

Reproducible with: 2017.4.11f1, 2017.4.34f1, 2018.4.13f1, 2019.2.0a8, 2019.2.13f1, 2019.3.0b11, 2020.1.0a13
Not reproducible with: 2017.4.10f1, 2018.4.3f1, 2019.2.0b6, 2019.3.0a6,

Comments (12)

asad627

Dec 01, 2019 14:50

This was a really great contest and hopefully I can attend the next one. It was alot of fun and I really enjoyed myself..
https://www.jupitertreepros.com/
asad627

Dec 01, 2019 14:49

This was a really great contest and hopefully I can attend the next one. It was alot of fun and I really enjoyed myself.. <a href="https://www.jupitertreepros.com/">coconut removal Jupiter FL</a>
unity_7tLMXeHeV6Xzdw

Nov 30, 2019 09:32

Superbly written article, if only all bloggers offered the same content as you, the internet would be a far better place.. 사설토토사이트
unity_7tLMXeHeV6Xzdw

Nov 30, 2019 09:32

Superbly written article, if only all bloggers offered the same content as you, the internet would be a far better place..
[url=http://motosportpro.com/]사설토토사이트[/url]
unity_7tLMXeHeV6Xzdw

Nov 30, 2019 09:31

Superbly written article, if only all bloggers offered the same content as you, the internet would be a far better place.. <a href="http://motosportpro.com/">사설토토사이트</a>
cullen_unity

Nov 07, 2019 14:49

have this issue using 2019.2.9
hadowmaru

Oct 29, 2019 16:31

I have this issue on 2019.2.1 i was using IL2CPP configuration for android, to turn around i switched back to mono and then brakepoints worked again.

Project Settings > Other Settings > Scripting Backend - Mono, Net Standard 2.0, ARMV 7.

Note: When i have to build for google i switch back to IL2CPP...
Ziflin

Oct 23, 2019 15:30

This is *NOT* fixed in 2019.3.0b4 and is *SUPER* annoying. Please fix again! :)
Twelewen

Aug 24, 2019 11:30

Here is a solution how I am able to debug any code without any issue now. I have been having this issue for 5 years so far making me wanna jump out of the window many times. Here is a list of checks I am doing before every debuging sesion and I haven't experienced a single debugging issue since than. Some steps may be ommited probably

- Detach Visual Studio debuger from Unity
- Stop unity project running if any
- Recompile your solution (deploy DLLs into plugin directory)
- Let Unity recompile imported DLLs
- Reimport all plugin directory in Unity (wait for the work-in-progress bar)
- Visual studio start doing dome heavy work (you can check in Task Manager cpu load). You need to wait till it finish processing and if you interrupt this process either by Unity Run button or attaching Visual Studio debuger to Unity you ended up with non-working breakpoints. Wait till you see the heavy cpu work is done in Task Manager - took 20 sec for me.
- Hit Unity play button and wait till it starts
- Attach Unity Debugger
FlightFight

May 08, 2019 13:05

ShikenNugget's solution worked for me in Visual Studio 2019

"Go Project Settings -> Player -> Other Settings and set the API Compatibility level to .NET 2.0 (as opposed to .NET 2.0 Subset). Restart Visual Studio, Clean and Rebuild the solution. This got rid of the warnings for me. "