This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
1PW-Mac & iPhone: Sync (WiFi) issues
Mac: 1Password 3.5.8 (build 30881)
iPhone 4G: 1Password Pro 3.5.7
Sync via WiFi local (not Dropbox)
(actually, none is Beta, but I am posting it here anyhow).
The sync didn't have any problems for a very long time, or at least I didn't pay attention to small details 9se below).
This time I see some anomalies:
[list=1]
[*]
1PW on Mac was open, unlocked.
I launched the 1PW and unlocked it (4-dig lock).
Checked the More>Settings>(WiFi)>Sync>WiFi Sync>History:
[code]10 seconds ago:
<day-time...> Accepting new connection
<day-time...> Closing connection[/code]
Checked 1 entry that I know that it was supposed to change, but it didn't.
Checking 1PW-Mac:
[code]
Last Wi-Fi synced: 12 days
[/code]
So the Mac side was not aware of the sync.
I later did a manual sync, and all worked fine, ie: all syncs were performed.
So - I don't know what happened the first time.
[*] I now realized that there is one entry that is being synced every time, even if it was not updated. Checking in old histories, I see that starting 21 weeks ago, there is the same entry (in addition to any entries changes that happen to be):
[code]
...
<day-time... GMT> Sending '....<entry-A>...' [....id...]
<day-time... GMT> Scheduled to send 1/1 updates
<day-time... GMT> < sync
<day-time... GMT> Closing connection
[/code]
What is the meaning of "cheduled to send 1/1 updates"? and usually it is just 1/1, (or 2/2 sometimes), even if more entries were synched.
And why entry-A is 'stuck' there?
BTW: about 14 weeks ago, the format of <day-time... GMT> changed to <day-time... +0000>, not that it matter to me.
[/list]
iPhone 4G: 1Password Pro 3.5.7
Sync via WiFi local (not Dropbox)
(actually, none is Beta, but I am posting it here anyhow).
The sync didn't have any problems for a very long time, or at least I didn't pay attention to small details 9se below).
This time I see some anomalies:
[list=1]
[*]
1PW on Mac was open, unlocked.
I launched the 1PW and unlocked it (4-dig lock).
Checked the More>Settings>(WiFi)>Sync>WiFi Sync>History:
[code]10 seconds ago:
<day-time...> Accepting new connection
<day-time...> Closing connection[/code]
Checked 1 entry that I know that it was supposed to change, but it didn't.
Checking 1PW-Mac:
[code]
Last Wi-Fi synced: 12 days
[/code]
So the Mac side was not aware of the sync.
I later did a manual sync, and all worked fine, ie: all syncs were performed.
So - I don't know what happened the first time.
[*] I now realized that there is one entry that is being synced every time, even if it was not updated. Checking in old histories, I see that starting 21 weeks ago, there is the same entry (in addition to any entries changes that happen to be):
[code]
...
<day-time... GMT> Sending '....<entry-A>...' [....id...]
<day-time... GMT> Scheduled to send 1/1 updates
<day-time... GMT> < sync
<day-time... GMT> Closing connection
[/code]
What is the meaning of "cheduled to send 1/1 updates"? and usually it is just 1/1, (or 2/2 sometimes), even if more entries were synched.
And why entry-A is 'stuck' there?
BTW: about 14 weeks ago, the format of <day-time... GMT> changed to <day-time... +0000>, not that it matter to me.
[/list]
Flag
0
Comments
-
Hi Locker,
This is strange. Can you open 1Password on the Mac, select the iPhone on the left sidebar under the Sync heading and then check the “Replace the Information on this iPhone”. Press “Sync Now” to send the entire keychain from Mac to your iPhone:
[img]http://cdn.agile.ws/mike/helpdesk/Replace_Info_on_iOS_with_Mac.png[/img]
Let me know how it turns out,Flag 0 -
[quote name='MikeT' timestamp='1299545823' post='22022']
...
Let me know how it turns out,
[/quote]
I performed the “Replace the Information on this iPhone”. (after saving a backup from the iPhone to the Mac, as precaution).
Once it finished, I exited 1PW on the iPhone and relaunched it. The next (normal) sync seems to be good now. This time, no entry was synced or scheduled to be sent. So it all looks good now.
[code]
<day-time +000> Accepting new connection
<day-time +000> handshake
<day-time +000> Master password was not entered, SL5 key is not available
<day-time +000> Authenticating '...' [...]
<day-time +000> < handshake
<day-time +000> > start
<day-time +000> < start
<day-time +000> Closing connection
[/code]
BTW: What are the implications of "Master password was not entered, SL5 key is not available"?Flag 0
