"Sending message header failed" warning

I get a warning in my console when running a standalone dev build (mac). The warning is "Sending message header failed". I'm wondering if it might have anything to do with why my behaviour that handles scene switching isn't working.

 

You get this figured out? I get this problem too - only in a development build.

 

No, nothing, sorry.

 

Same issue here.

 

I'm also seeing this issue, using Unity 5.0.0p3 and OSX 10.10.1.

Looking at Console.app there's more information being logged outside of the Unity error window.

I believe I had the platform set to iOS at the time these errors were printed.
The following are the iOS platform settings:
SymlinkUnityLibraries = true;
DevelopmentBuild = true;
AutoconnectProfiler = false;
ScriptDebugging = true;

The following is always called exactly as printed some time around when I'm using the Build window.

Native extension for OSXStandalone target not found
Native extension for WindowsStandalone target not found
Native extension for LinuxStandalone target not found
Native extension for WebGL target not found
Native extension for BlackBerry target not found
Native extension for Android target not found
Sending message header failed

(Filename: /Users/builduser/buildslave/unity/build/Runtime/Network/PlayerCommunicator/GeneralConnection.cpp Line: 345)

Sending message header failed

(Filename: /Users/builduser/buildslave/unity/build/Runtime/Network/PlayerCommunicator/GeneralConnection.cpp Line: 345)

After further research I've found it prints after I resume back to Unity from closing xCode after building.

 

I also have this warning. Generally it appears after running an app with profiler connected.

In the log:
Sending message header failed

(Filename: /Users/builduser/buildslave/unity/build/Runtime/Network/PlayerCommunicator/GeneralConnection.cpp Line: 345)

 

Same thing happened to me today. I had profiler open running my game on android. Not sure why it happened though.

 

The only annoyance is when the message is continually sent until you restart Unity... You can also open the profiler and change the "Active profiler" to something else than what caused the "lost connection" in the first place. It should stop.

 

Same message here - happens when I close the game on windows (both x86 and 64 builds) with dev build/debugging enabled in the build options.

 

The same is in my case. Have you found anything? (even when running without profiler)

 

I'm seeing this in 5.1.2 - has anyone worked out the cause yet?

 

anyone got fix for this?, i already done everything i read on unity wiki profiler, still got this error

 

On Android developing, I solved this issue by "build and run" with USB cable (not transferring apk via Dropbox).

 

Still a bug. Happens when the development build is running with possible profiler attached. If the profiler isn't running, the error keeps spamming the console even after the build is closed :/

 

I have also seen this after running the profiler on an app that has since been closed. I often have to completely close Unity and open it again to be able to attach to the same device.

 

Yeah, I can confirm this happens also on PC when you enable script debugging in dev build, run it once and close it. Not amazed that this issue was already discovered back in 2015...

 

Ifdef_ben's answer worked for me: Go to profiler and choose "Editor" as active profiler.
http://answers.unity3d.com/answers/1250153/view.html

 

This is only a temporary workaround, and the messages often come back for me after following the steps mentioned in that Answers question. For whatever reason -- even if the Autoconnect Profiler option is disabled in the built game -- Unity still tries to autoconnect the profiler in the editor. It's incredibly annoying. Anyhow, I've filed a bug (877573) in case one doesn't exist yet.

On a related note, since I don't see anyone else in this thread mention having submitted a bug report, please realize as developers that Unity relies on us to report these things for visibility, and "me too"ing these posts without reporting a bug rarely solves the problem. If you have reported it and just didn't mention it, apologies.

 

It happens when a profiler connected to Unity via a network is abruptly disconnected. Changing the Active Profiler to editor fixes this.

 

@bik3r014 I'm not sure if you're just "me too'ing" this post or if you missed the posts above that describe the same workaround you posted, but be assured that is not a "fix." This is a bug in Unity that currently only has an annoying workaround.

The good news is that the bug I created was marked as a duplicate of this bug, which currently has a "fix in review." Here's hoping it gets backported to the 5.5 branch!

 

@adamt Since this is a forum page(and not Answers), I thought it'd be a good idea to chip in with a solution that works for me. Interestingly, the solution still works for me, but I realize mine could be a one-off thing. If guys here don't like 'me too's, I'll refrain from posting. Thanks for the heads up!