The other collection of Documents seem to be synching ok. That said, I think I identified the isolated area down to one collection of forms contained within my “Media Library” documents. I really don’t believe this is sync issue as much as some sort of file corruption. In other words, I understand the differences between the two sync options I’ve tried.
But the app still hangs with both devices open and next to each other.
CLOUD SYNC TAP FORMS MANUAL
Even trying to initiate a manual sync (using the sync button) produces no response. It’s like the app just gets hung-up on the iPad and needs a kick in the ass to pick up those changes. And for the record, I encountered the same behavior when using both iCloud Sync (which is very convenient when it works) and Nearby Sync. Sam, Yes, you are correct I tried that twice already.
CLOUD SYNC TAP FORMS MAC
Seems similar to what just reported (#44977) except his issue deals with iPad -> Mac vs. If I close the app when finished w/o remembering to re-open/re-close the app on iPad to force a sync I will lose all but those initial first few edits I made if I even open the app on my phone and then return to the iPad later. After which, if I begin editing or adding records (still on the iPad) the first few edits work and appear to sync “as I go”. Again, when opening the app on iPad, the first thing the app does is checks for any pending changes and makes the appropriate updates. The only other thing I’d do is resend a clean copy of the database from a master device and replace the others but I gather you’ve already done it.īrendan, to answer your question, Yes… even the smallest database presents issues but only on the iPad. By default that will only work whilst your Mac is on, CouchDB is running and you’re on your network but that might make things a little more stable or at least give you a more interesting error message. This is different to the pull only model of nearby sync.
The CouchDB sync is bidirectional so that it will both push changes as they happen to the server but also will pull the changes as they happen so other devices see them quickly. Personally I’d look at setting up Apache CouchDB on your Mac and let it run in the background then use it to sync. That does mean the app needs to be open and in the foreground for the sync to happen on iOS devices though I gather that’s likely not the problem. The nearby sync works by pulling changes from other devices which works around a certain amount of issues because it’s not pushing the change. I wonder if there is a poison record somewhere gumming up the works. That said, open to feedback and suggestions. That said, as much as I love Tap Forms, I find myself looking for an alternative as I continue to lose hours’ worth of valuable work unless I consciously remember to “force sync” my changes by quitting and restarting the app every time I make a change that I want to stick. However, Tap Forms is the only app that gives me synching issues on my iPad. The only difference between to the two devices is my phone is Wi-Fi + Cellular, whereas my iPad is Wi-Fi only.
I have tried everything from using Nearby Sync (instead of iCloud), to re-copying the databases from my phone phone back to my iPad, backing up and restoring, reinstalling the app completely, building a new test app on my iPad to see if perhaps it’s just those existing databases impacted, etc… and all to no avail. In the meantime, if I open the app on my iPhone and make any changes, the next time I launch the app on my iPad any previously made “iPad” changes are overwritten by my recent changes made while using my phone. After making a few changes, those changes are “saved” to the device but NOT synched back to the cloud unless I close and re-open the app to “kick-start” the synching process.
CLOUD SYNC TAP FORMS PRO
I am synching Tap Forms between two iOS devices via iCloud but continue to experience issues when doing so using my iPad Pro.ĭevice 1: iPhone 12 Pro (iOS 14.7.1) – Syncs flawlessly to the cloud every time.ĭevice 2: iPad Pro (iOS 14.7.1) – Only syncs when the app is initially opened.
0 kommentar(er)
