iOS sync on iPhone 4 works a few days, then stops
I don't have any firewalls running, and this is my console:
svc removed: BiJoliPhoNeLoFono
type:mdncsync.tcp.local.
svc added: BiJoliPhoNeLoFono type:mdncsync.tcp.local.
requested service info svc resolved: BiJoliPhoNeLoFono;
type:mdncsync.tcp.local.
attempting to sync with BiJoliPhoNeLoFono; URL: http://192.168.19.1:6366
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at com.moneydance.modules.features.netsync.Main.testKeyWithDevice(Main.java:352)
at com.moneydance.modules.features.netsync.Main.tryToSyncWithURL(Main.java:262)
at com.moneydance.modules.features.netsync.Main.access$300(Main.java:34)
at com.moneydance.modules.features.netsync.Main$SyncMonitor.serviceResolved(Main.java:499)
at javax.jmdns.impl.ListenerStatus$ServiceListenerStatus.serviceAdded(ListenerStatus.java:63)
at javax.jmdns.impl.JmDNSImpl$4.run(JmDNSImpl.java:1289)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
The IP con my iPhone is NOT http://192.168.19.1, but 192.168.1.115.
Please help me!!!
Support Staff 2 Posted by Jon Hoover on 05 Sep, 2011 09:45 PM
Hi,
We are aware that syncing for the Moneydance iphone/ipad app is not working well on some of our customer's network configurations. We apologize to those who have been affected by this. We have made it our top priority to redesign the syncing mechanism to address these issues.
The next release of the app will include a syncing mechanism that is immune to issues with local network and router configurations.
The new syncing mechanism will work in any network configuration and will not require both the desktop and device apps to be running at the same time. In addition, you will be able sync anywhere you have internet access.
We are excited to roll out this fall an app with bulletproof connectivity that maintains the same standards of security and reliability you've found in the desktop version of Moneydance.
We appreciate the patience that the Moneydance community who is affected by syncing issues has given us to figure out the best new implementation.
Sincerely,
Jon Hoover, Moneydance Support
3 Posted by James Walley on 14 Sep, 2011 04:38 AM
I'm very glad to hear your plans for the next version. Do you have any idea when it will be released? I'm right on the verge of upgrading my Palm Pre to an iPhone when they are released for Sprint next month (which would mean going from Quicken/Pocket Quicken to MoneyDance), but would be hesitant to trade in a solution that's currently working for one that isn't but is promised to Real Soon Now. Should I be looking to upgrade to the iPhone in the near future, or should I plan to hold off for a few weeks/months because it's unlikely the revised MD app will be ready until then?
4 Posted by martin.j.lowe on 27 Sep, 2011 05:30 PM
I also hope that the syncing issue can be sorted out.
Last night I was able to sync desktop changes to the iPhone, but today made the foolish mistake of making entries on the phone at lunchtime and expected them to sync back to the desktop.
Have thrown the receipts away as well :-(
5 Posted by larry on 20 Oct, 2011 04:42 PM
I wrestled with the challenges of getting Moneydance to sync with my iPhone for several months. Sometimes I would have to open the IOS app multiple times to get it to sync. Other times, I would open it several times with no success.
I finally figured out a way that seems to work every time. If you open the App on your iPhone first, then open the desktop app, it seems to sync the first time every time.
Hope this works for others. It's a great desktop and app combo. The syncing issue was the only major shortcoming that was frustrating me.
6 Posted by James Walley on 25 Oct, 2011 02:00 PM
larry --
Interestingly, for me, it's the exact opposite. Opening the app first, and the program second, is a sure guarantee for it NOT to sync. Instead, I always have to open it on the desktop first, wait until it has finished updating stock prices, save the desktop data file if needed, and then open the iPhone app and sync is the only reliable way to get it to update on my system.
I must say I find it a bit distressing that the powers that be are still rolling out the same boilerplate "We are excited to roll out this fall..." response at the end of October that they were posting at the beginning of September. Surely you'd think that they'd have made some sort of progress toward actually finishing the app in the past six weeks. The fact that we're still getting the same form letter suggests to me that the new app they're so excited about may be released in fall, but I'm not sure WHICH fall...
Support Staff 7 Posted by Jon Hoover on 27 Oct, 2011 11:24 PM
James,
I never thought of myself as 'the powers that be' but I suppose that's better then some names that I could be called ;-)
Our lead developer today said he is hoping to have the code working and ready for testing by Halloween. Depending on how well it tests it could be sooner or later after that date but it is certainly still on track for the fall.
Please let us know if you have any more questions.
Sincerely,
Jon Hoover, Moneydance Support
8 Posted by James Walley on 27 Oct, 2011 11:33 PM
That would be great. By the way, and I should probably post this in the forum, I personally haven't had a problem with the current version, but one can't be too safe.
Sent from my iPhone