View Single Post
Old 04-13-2017, 04:49 PM   #18
Steve_Haley
CC iOS Developer
Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.
 
Posts: 142
Karma: 53024
Join Date: Jul 2012
Location: England
Device: Variety phones/tablets
Quote:
Originally Posted by chaley View Post
Given what The Old Man said, calibre didn't connect. It is rare but not unheard of for an antivirus to allow the broadcast "Are you there" messages to get to calibre and to let calibre respond, but then to prevent actual connection attempt from CC.
The weird part is that it got far further than just responding to the "Are you there?" broadcast. For example, here's an anonymised excerpt from the log:

Spoiler:
SMART_DEV ( 17.24: 0.015) _call_client GET_INITIALIZATION_INFO wfr True
SMART_DEV ( 17.41: 0.156) open Device can stream books True
SMART_DEV ( 17.41: 0.000) open Device can stream metadata True
SMART_DEV ( 17.42: 0.000) open Device can receive book binary True
SMART_DEV ( 17.44: 0.000) open Device can delete multiple books True
SMART_DEV ( 17.46: 0.000) open Device can use cached metadata True
SMART_DEV ( 17.46: 0.000) open Cache uses lpaths True
SMART_DEV ( 17.47: 0.000) open Can send OK to sendbook True
SMART_DEV ( 17.49: 0.000) open Can accept library info True
SMART_DEV ( 17.49: 0.000) open Will ask for update books True
SMART_DEV ( 17.50: 0.000) open Will set temp mark when syncing read False
SMART_DEV ( 17.52: 0.000) open Client device kind iPad
SMART_DEV ( 17.52: 0.000) open Client device name [redacted] Mini 4
SMART_DEV ( 17.53: 0.000) open Client app name CalibreCompanion
SMART_DEV ( 17.55: 0.000) open App version #: 128


It knows it's connected to CC (and the version it's connected to), as well as having the device's name. This means it definitely got further than just the initial broadcast since it has started the initial sync process.

Upon further examination I can see that it does report an error later on.

Spoiler:
SMART_DEV ( 142.34: 0.000) _receive_from_client protocol error -- empty json string
SMART_DEV ( 142.36: 0.000) _call_client other exception
Traceback (most recent call last):
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 615, in _call_client
File "site-packages\calibre\devices\smart_device_app\driver.p y", line 657, in _receive_from_client
ControlError: Device responded with incorrect information


Quote:
In any case it apparently is not the fault of CC. Thank you all for your help and suggestions.
Anyway, I'm glad you got it working in the end even if you had to use another computer!
Steve_Haley is offline   Reply With Quote