UWP IL2CPP debug port number?

Is it possible to retrieve the port number used to connect a manager debugger at runtime in a UWP player? I'm often working in a network the multicast advertisement process doesn't work and I need to enter that value manually.

I've heard that for the editor and perhaps certain other platforms that this is inferred from the process ID but that doesn't appear to be the case for UWP. The only place I seem to be able to find this number is by running the app from Visual Studio, watching for the logged profiler multicast message (example below) and noting the last three digits of the "GUID" in that message, which seems to match the last 3 digits of the debug port.



What does this GUID correspond to and can I access it at runtime in a script? It would be enormously helpful to be able to display this somewhere inside the app as required.

 

Thanks! I do hate it but parsing the player log at least sounds like a viable workaround for now

Not sure if there's an official channel for providing this sort of feedback but given the discovery process can be very difficult to use inside an enterprise network:

• It'd be really useful to have this GUID or derived port number properly exposed to applications somehow e.g. Application.debugPort or something
• Would also be really useful to display the port number on the "you may attach a managed debugger now if you want" dialog when enabled
  
• Not sure if this is a UWP specific thing but certain devices (e.g. HoloLens 2) have some TCP/IP over USB functionality. This'll have a valid IPv4 address to which both the managed debugger and Unity profiler can be manually attached if you know the port numbers (which is tricky sometimes as per this thread). However the multicast discovery process seems to ignore this, typically utilizing only the primary 802.11 adapter. If a development player would multicast one packet per adapter with the corresponding IP, including the USB adapter, the automated discovery process might "just work" over USB and mitigate a lot of the difficulties here.

[EDIT] For anyone that stumbles upon this, reading the player log isn't the solution, it appears to be locked by whatever is writing it and any attempt to read it at runtime results in a sharing violation. Ended up creating a socket in app code to join the multicast group which allows me to see the outbound message, parse out the port and expose it however I need. Hopefully in future this won't be necessary.

 

This is absurdly annoying. I have to attach the debugger to an instance where I dont know the port ahead of time. And it crashes on launch, which Im trying to debug. So I have less than 10 seconds to attach the debugger to a port I cant read until the countdown starts.

What kind of absurd design is this? It's so counter intuitive.

 

Have you tried the "Wait for Managed Debugger" option? If enabled, the application should not proceed to start until the debugger is attached.

 

Yes I have, that's the problem if you read my comment. You enable that, and Unity starts counting down from 10 waiting for the debugger. You have 10 seconds to find the port from the log, and input it into the debugger. Even then, sometimes it doesn't work until you time it just after 0 on the timer. You can't know the port ahead of time, it's super silly.

 

It's a headless mode -nographics app, so it's not going to pop up a message box.
It's a hard app crash. I have a ticket open with unity, looks like my particular crash is related to Incremental GarbageCollection issues somewhere in Unity on Linux. But it's all kind of irrelevant, we should be able to specify or grab port number somehow.

 

Also, just found out it is not just headless/nographics standalone that does the countdown from 10 seconds.
It's also on Android devices (shows up in logcat). I presume iOS as well.