No matter what I try, I can no longer convince the iPhone app to detect the MacOS library. Same wifi network, latest versions of all relevant software (OS, Library, Scanner); tried rebooting, deleting + reinstalling, etc.
Is this a known issue? It simply doesn't connect anymore.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
MacOS Yosemite, Delicious Monster 3.3.5, iPhone scanner 1.0 not pairing
-
Matt
There are still issues with Yosemite's networking functionality, so any issues you are seeign could be attributed to that. Having said that, the issues I personally were seeing were resolved in 10.10.1
so onto diagnosis, if you can answer these questions, it may help to diagnose or even resolve your issue
Do you have bluetooth enabled on your phone? turn it off, does this resolve the issue?
Is your Mac on WiFi or connected to your router via network cable? If cable, unplug the cable and connect to wifi.
Is your phone connected to your WiFi on that router, or on another base station/extender? Turn off any mesh networks, or base station extenders so both the device and your mac are connected to the same wifi hub. -
-
Stu,
1. Bluetooth: no, it is off, changing it has no impact.
2. WiFi, same WiFi network as on phone.
3. I'm not running any mesh networks or using any base station extenders. They're both on the same network; I've tried having them both on the 2.4 and 5G networks. No difference.
Thanks for your response, though! -
-
Can you change the name of your IOS device?
If its something like the default of "Matt's iPhone", change it to something else, reboot and try to pair again. -
-
I tried changing the name, rebooting, and pairing again, but unfortunately that didn't work either :(.
-
-
ok, i'm not out of ideas but we are down to grey areas.
Things i would check again.
Do you have any VPN software installed and running in task bar?
Do you have Little Snitch or similar firewall running?
Are both devices on the same WiFi network running with DHCP and do the network name and settings match (IP range/Mask and gateway IP addresses)
Do you have any other adhoc networking devices enabled (Thunderbolt display networking etc, Bluetooth PAN)
Since it would appear that it's the iOS device doing the searching for the app on Mac, and again assumimg that Bonjour is the protocol, I think I'm going to go play with this app later today to see if I can see any comms that might have diagnose other peoples issues.
https://itunes.apple.com/us/app/disco... -
-
Ok, interesting stuff. The Mac App and the Scanner app both are talking over bonjour on the 'local' domain.
The mac app is broadcasting over:
_deliciousscannerhost._tcp and _dmscannerhost._tcp
The iOS app broadcasts on:
_deliciousscannerclient._tcp
If you can download the iOS app I linked in the previous post (its free), I'd love to see if your iOS device can see the bonjour messages being broadcast by your mac.
The OS X app is also available for free, http://tildesoft.com if you can download and run that, this will at least tell us if your mac can see the iOS app, and vice versa
-
-
I have same problem.
Have not used DM for a while - hardware is the same but OS X and iOS have all been upgraded since the scanning worked for me
DM 3.3.5
OS X 10.10.2
iOS 8.1.3 -
-
I will give the 'Bonjour Browser' a try and paste up my results ..............
-
-
have you tried to re-pair?
have you tried any of the apps above to see if you can see the same Bonjour items? -
-
I haven't had time to try the bonjour browser business yet. It'll be interesting to see if there's anything of note there.
-
-
Yes I have tried to re-pair many times.
Also have removed DM and the scanner app, reinstalled (rebooted) and tried again.
I will try the diagnostic app noted above .............. -
-
BTW when I try to pair a second time the iOS app reports it is already paired however the '..........library not detected' message remains
-
-
I have this same problem. I have also received the "already paired" notification with the "library not detected" message at the same time.
-
-
Bonjour Browser is now on my Mac
Both Mac and iPhone are connected (wirelessly) to my home network
DM3 is loaded
Load scanner app on iPhone and perform pairing.
Bonjour Browser reports
_deliciousscannerhost._tcp. - 1 and
_dmscannerhost._tcp. - 1 and
_whats-my-name._tcp. - 1
running but nothing else.
So
_deliciousscannerclient._tcp is not being seen -
-
Steve
Your iPhone can't see part of your network at a guess.
What make and model is your wireless router?
Is uPNP enabled on the router? -
-
-
-
The only other thing that I can think of, since the above is showing that incoming connections are being blocked (which can be router or firewall), that this might be a Yosemite Firewall issue.
It used to be that you had to ensure that mDNSResponder was in the allowed list of applications. mDNSresponder no longer exists in Yosemite and the replacement is called "discoveryd"
Also there is a checkbox that says only allow signed apps to communicate. If you have this checked and you use the application downloaded direct from Delicious Monster (and not the App Store version), this might be causing an issue.
Anyone with this issue, can you ensure that discoveryd and the Delicious Library.app are in the allowed list of applications.
Anyone with different firewalls you should ensure that the ports used for Bonjour are not being blocked. A list of ports used by Apple is linked below, just ensure that the Bonjour ports are free to communicate.
http://support.apple.com/en-gb/HT202944-
Where is that discoveryd? I don't find any such item when in the OS X Yosemite System Preferences > Security & Privacy > Firewall pane I try to add it.
-
-
Oh: I see now that the released 10.10.4 actually restored mDNSResponder and took away discoveryd.
-
-
-
-
-
Thanks for your help Stu
FWIW uPNP is enabled and my router is a Technicolor TG582n FTTC.
They are supplied by a number of ISPs in the UK when you go for Fibre broadband.
I put Bonjour Browser on my iphone and found a version for my Win7 PC - http://hobbyistsoftware.com/bonjourbr...
The Win7 PC shows _deliciousscannerclient._tcp when the scanning app is loaded on the phone. The Win7 PC is Ethernet cable-connected to my router.
I am a newbie as far as OS X is concerned but will follow up your suggestion above and use this as a learning experience !- view 3 more comments
-
-
-
-
Thanks for the prompt reply.
I shall sort this - are there any other diagnostics I could run and supply to help with this.
Would it be easier to email the outputs ? -
-
A screenshot of the IOS device Wifi connection properties would be good also, that'll help determine if the two devices are both using the same network configuration. There'll be a few screenshots, so if you want to send direct to me at dammitjanet a.t. me.com I'll see if I can have a look as son as I get them.
-
-
-
-
CHAMP
1Ok after a few emails back and forth, the issue was isolated to Steve's router which was not allowing traffic between devices both connected to the router's wifi
Traffic could flow from Wifi devices to devices connected to the router's Ethernet ports, but two devices both connected to Wifi could not see each other.
For his router there was a checkbox in the uPnP configuration "Use Extended security" that when unchecked allowed the devices to see each other. As I've advised Steve, this is probably not the best solution since this does leave his router less secure.-
Thanks Stu and point taken re the router setting but I can do my scanning in sessions so enabling/disabling is not a problem.
Just happy I can continue scanning ! -
-
-
-
-
For me, the "pairing" and "OS X Library Not Detected" issue is solved.
Using screenshots and reports Stu (Wilson) was able to identify the problem area as the router and a router setting related to UPnP.
The router in question is the Technicolor TG582n FTTC (supplied by PlusNet and other UK ISPs). On the modem configuration pages you can enable/disable UPnP and also enable/disable "Extended Security"
UPnP and "Extended Security" enabled DID NOT allow the iOS scanner app to connect to DM3
UPnP enabled and "Extended Security" disabled DID.
Yay! -
Loading Profile...





