We are happy that our fruux v0.7 rollout went quite smoothly.

However we’re still not entirely satisfied, because some of you are affected by bugs.
There are currently three known issues with iCal syncing:

• if you heavily use recurring events, your sync might break (we’re working on this one)
• Obviously some of our users from russia are affected by an encoding bug (we’re working on this one)
• Some users have problems with duplication and repeating sync conflicts (so far all of them used other sync systems in addition to fruux, we’re working on this one, too)

Only very few users are struck by those bugs, but still we are extremely sorry for any inconvenience caused! Please keep in mind that fruux is still in beta. We’re working really hard fixing those bugs as fast as possible.

If you are affected by bugs or need help, please get in touch with us:
support (at) fruux . com

(Please don’t forget to enter your correct emailaddress, if you use our contact form. If you email directly to our support emailaddress, please include the file ~/Library/Application Support/Fruux/Sync.log).

Some of our users already work with our addressbook syncing in productive enviroments. If you need addressbook syncing e.g. in your office and there is no way you could wait for our bugfix release, please contact us. We might be able to offer you a customized version of fruux, which just syncs your addressbook.

Please do not hesitate to contact us if you have any problems concerning fruux! Thank you for your support.

fruux is meant to simplify your digital life. When syncing different devices and services you might run into troubles called sync conflicts.

Just think about the following scenario:

1. you modified one of your contacts phonenumbers on the go via the (not yet demoed) fruux webapplication
2. then you modified the very same contacts phonenumber on your laptop (lets assume you had no internet access while doing this)

The outcome of this example is a sync conflict. The fruuxServer and your local system now contain different phonenumbers for the same contact. As the system has no idea which phonenumber is the correct one, it just asks you.

Reviewing the sync conflict gives you a nice dialogue (left side shows your local addressbook, right side shows the data from the fruuxServer). Now it’s really easy to choose the correct contact, by just clicking on the correct card.

After choosing the correct card you just restart the sync via the “Sync Now” button and immediately both your local system and the fruuxServer are in sync again.