Q: How to locally sync an iPhone with OS X Mavericks? iCloud is NOT an option.

Armando Stettner wrote:

 

That's ok.  As they control both sides of the 'equation' (Calendar/OSX and iOS), there was no reason to change.  CalDAV/CardDAV would have worked just fine via the local sync.

Sure there was. No need to maintain old, crappy code. Use open source that is known reliable and compatible with almost everything. The decision to drop that code was done over two years ago.

They could have implemented a server within the client version of OS X, but they didn't.

Barney-15E wrote:

 

Armando Stettner wrote:

 

That's ok.  As they control both sides of the 'equation' (Calendar/OSX and iOS), there was no reason to change.  CalDAV/CardDAV would have worked just fine via the local sync.

Sure there was. No need to maintain old, crappy code. Use open source that is known reliable and compatible with almost everything. The decision to drop that code was done over two years ago.

 

They could have implemented a server within the client version of OS X, but they didn't.

Sorry; I wasn't clear.  There was no reason to change the METHODS from the users' perspectives.  As you say, the open source that is known  reliable and compatible with almost everything could easily have supported the local USB sync - in addition to the iCloud mechanism.

As you say, the open source that is known  reliable and compatible with almost everything could easily have supported the local USB sync - in addition to the iCloud mechanism.

Read my last sentence again.

I did.  I was less concerned with implementation underpinnings and more with functionality.

"That's why Apple abandoned 'sync' and found a better method, iCloud."

... I don't see how 'sync' has gotten any better? It no longer exists!

Isn't this thead about how to local sync? We all know about iCloud and how good it is.

We're not here because of iCloud, we are her because of local sync, with USB.

Armando Stettner wrote:

 

I did.  I was less concerned with implementation underpinnings and more with functionality.

Well, without understanding the underpinnings, you can't understand the decision.

SyncServices worked poorly--lots of conflicts and duplicated contacts. Apple had to maintain and update the code to make it work, and continue to work.

With CalDAV and CardDAV, little to no code to maintain. No conflicts to speak of as the last in wins. I haven't seen any duplicated contacts or events, either. But, I am only a single data point.

A lot of people have issues with duplicated calendars and contacts but this is usually a bug or issue that was carried over from MobileMe, one bad sync and the clouds hit the fan. I see this at least five times a week.

iCloud on it's own, without it being an upgrade from MobileMe (as far as I have seen) has not had any of those issues.

Good thing is tho, it shows third party interest in a solution. AAPL may never bring the function back but we have a start.

It's not too much of a stretch I think to assume that this developers product will improve or that other alternatives will appear.

btw - got anybody a response from apple when sending a message to complain about the bad situation?

I never heard anything.

Maybe they can do it the next time: http://www.eltima.com/

Saw that SyncMate a while back. Haven't moved on it yet as it's not 10.9 ready and there's obviously been no pertinent reviews.

But no, I've had no official feedback.

tekknosaurus

try Chronosync and SyncBack Pro  recommended to me by the renowned David Gerwitz

Who?

Pete

feinmeister wrote:

 

tekknosaurus

 

try Chronosync and SyncBack Pro  recommended to me by the renowned David Gerwitz

I think both those tools are backup tools to incrementally copy files to a backup drive and sync documents between devices, not for syncing contacts and calendar between devices?  We have Time Machine and idevice sync/backup/restore via itunes to do all that.

Sorry if this has already been suggested -- I have read nearly all 144 pages of posts, but admittedly I may have missed something, so sorry if this is a repeat.

I am trying the following solution. Perhaps it will work for you and for others.

I am slowly migrating away from Address Book altogether, over to a secure alternative, STRIP, by Zetetic. (NOTE, I have no affiliation with the company, and there may be many other similar products that do the same thing. I just happen to have found this one to work well enough for my needs so far).

STRIP is a password manager and "data vault."  The data-vault part allows you to define any kind of records you like, with any kind of fields that you like. It is also smart enough to recognize phone numbers, URLs, and email addresses so that they may cause the iphone to dial a number or generate an email directly. (There are some configuration hassles to make this work, but it does work.)   Advantages are:

• Data at rest is encrypted, and apparently pretty well. You can search for validation of that claim.
• Can sync between iOS and OSX using local WiFi (no cloud)
• Can also sync through dropbox or google drive (undesirable based on the original poster's needs), BUT, the data that sits on dropbox or google is encrypted. The cloud provider never gets the data in clear form.
• Can import and export data as .csv files
• No need to set up and maintain a server (or be subject to revisions in server software)

My process has been:

1. gradually export different categories of my Address Book to .csv files (see App Store for a solution)

2. clean up the .csv columns so that they will match up with the field names I want for STRIP (e.g. for STRIP to recognize an email address, the column name MUST be 'email', etc.  Search for STRIP's import guide for more info, also STRIP's FAQ on how to work with other apps)

3. import the CSVs into STRIP on OSX

4. install STRIP on iphone

5. set up WiFi sync on OSX and iphone (see STRIP FAQ for how to do this).  I ~believe~ the data will only pass through my LAN and not go anywhere else in the process, and that the sync flows are encrypted

6. Sync to iPhone

7. Test everything out.

At the moment I am running duplicate contact lists -- one in STRIP and the old one in Address Book.  If the STRIP list remains stable and useable over a few months, then I will just export my Address Book contacts to .csv for the last time and delete the Address Book contacts locally and on icloud.  

You can also replace iOS / OSX Notes syncing with STRIP in the same way.  Not sure about an alternative to iCal though.

You obviously lose some of the benefits of Address Book like being able to automatically link contacts and the map. But to restore my privacy, I am willing to make that tradeoff.

Again - this is a viable workflow, not a push for any particular product. I happen to have found a solution via STRIP. There may be other similar software products that would allow the same end result.

Are there any issues / flaws (beyond what I have noted) that anyone sees in this sort of workflow?

Planner Plus appears to do the calendars bit. At the mo it's free too.

I don't mind having a second app for contacts, (assuming there is one).