This question is locked. New answers and comments are not allowed.
I've been using Kinvey as my BaaS for awhile now with my Icenium app and I had offline saving and syncing working great until recently. Everything seems to be working fine on the Kinvey side i.e. no failures or errors being generated but ever since Icenium became AppBuilder (At least from what I can gather) all of my offline stuff is busted.
I wish I had some kind of concrete error to give you but so far I can't seem to trap anything and I'm doing some pretty extensive error logging through my app :(
Kinvey relies on an IndexedDB implementation to do the offline saves and my only theory at this point is that something with AppBuilder is mucking with the IndexedDB side of things, not allowing anything to be persisted locally so once I execute the sync operation against Kinvey's backend, there's simply nothing there for it to sync, hence no errors generated on my end.
just a theory of course...I had this working great both on device (iOS and Android) and in the Icenium simulator but it's just DOA now. Working with Kinvey support to try and figure this out but was hoping somebody at Telerik might have an idea of what I'm running up against here???
I wish I had some kind of concrete error to give you but so far I can't seem to trap anything and I'm doing some pretty extensive error logging through my app :(
Kinvey relies on an IndexedDB implementation to do the offline saves and my only theory at this point is that something with AppBuilder is mucking with the IndexedDB side of things, not allowing anything to be persisted locally so once I execute the sync operation against Kinvey's backend, there's simply nothing there for it to sync, hence no errors generated on my end.
just a theory of course...I had this working great both on device (iOS and Android) and in the Icenium simulator but it's just DOA now. Working with Kinvey support to try and figure this out but was hoping somebody at Telerik might have an idea of what I'm running up against here???