-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Issues: NSLogger in app to desktop application #270
Comments
Quick update. Testing with device over wifi doesn't seem to have this issue. Appears to be simulator + wifi combination. hm... |
Seeing this issue as well. When running in the simulator with wifi no connection gets made between the app and the desktop app of NSLogger until some long (>30s) time elapses. If I disable Wifi upon app launch the connection gets setup correctly immediately. |
@jcarroll-mediafly @Donileo Did you see the method |
No, that seems the be when it dies off. That callback is never called. I believe the last set of calls I see in the console is about configuring / searching over bonjour. |
This is a really weird issue and I'm pretty sure there's something specific to your networking setup that makes it fail. When NSLogger tries to connect to the desktop, it already has the target info (IP address, port #) handy so this should definitely work ... unless networking calls are being routed out of the machine. Would you happen to have some specific networking options set in the sim ? |
I haven't completely tested my theory, but if I choose to not use the LOGGER_DEFAULT_OPTIONS but rather use all those options except Here is my console when I simply use defaults, no tweaking of options LoggerInit defaultLogger=0x0 |
@jcarroll-mediafly I can also confirm that excluding |
Thanks, @Donileo, your tip pointed me in the right direction, but in my case, I also had to disable SSL. |
I'm unsure if anyone else is experiencing this but I'm having major issues getting bonjour setup to work smoothly. The app / client side connects to NSLogger simply using
LoggerSetupBonjourForBuildUser()
. I'm running latest version (1.9) of the desktop app and I'm on Mojave, using XCode 10. Testing with iOS simulator.If I run NSLogger desktop app I can see the service running just fine. I confirmed by running
dns-sd -B _nslogger-ssl
and I can see the instance with the correct name.I've printed out debug statements and can see NSLogger is correctly trying to attach to the correct instance name, no problem.
Ultimately it just hangs and I see the console say
"-> configuring SSL"
"-> stream open attempt, waiting for open completion"
Eventually it will try again and usually fail. Maybe after 10 minutes it will connect. Not sure why.
I tried rebooting my router to see if anything funky was going on, and nothing really changed. However, during the reboot when I had no wifi connection it all of sudden started working?! I tested this theory by turning wifi on / off multiple times. If I turned off wifi it ALWAYS worked instantly, but as soon as I turned wifi back on, nslogger would go back to hanging with console output simply ending in "-> stream open attempt, waiting for open completion" again. Its great I found a way to get it to connect...however if my wifi is off I can't get that far into testing the application.
Note: This is my home setup. Which is almost 100% wifi, I don't necessarily have the means to easily plug in. I'm unsure if its a Wifi issue in general or specific to my router (I'm using an apple airport extreme). In the office on the other hand, I'm almost exclusively on wired ethernet, and I never seem to have issues there.
Curious to see if anyone else having issues.
The text was updated successfully, but these errors were encountered: