offline capabilities and auto-syncing

[marqueeeeeee]

Does this support offline saving and auto-sync when network is available? similar to saveEventually from parse sdk and firebase db? Thank you!

[RodrigoSMarques]

Hi @marqueeeeeee,
this feature is not available yet.

[frsisalima]

Hello, is the implementation of this feature planned? it would be great to have offline support

[monajafi]

we can implement saveEventually in android by caching saves if there is no connectivity then with the help of workmanager plugin which is a wrapper around android WorkManager we can sync the cached saves when the device connects to internet
This is easy in android but I'm trying to figure out how to implement in iOS because the background jobs are restricted in iOS we have just background fetch.
One point to have in mind about saveEventually is that there is no callback after saving
I have an app which is developed using native sdk If the server is down and device get connected to internet the save fails

[phillwiggins]

Hey Noida We should stick to keeping it pure Dart. We simply need a connection manager and a save pool of objects.

…

On Thu, Aug 22, 2019, 12:35 Mousa Najafi ***@***.***> wrote: we can implement saveEventually in android by caching saves if there is no connectivity then with help of workmanager plugin which is a wrapper around android WorkManager we can sync the cached saves when the device connects to internet This is easy in android but I'm trying to figure out how to implement in iOS because the background jobs are restricted in iOS we have just background fetch. One point to have in mind about saveEventually is that there is no callback after saving I have an app which is developed using native sdk If the server is down and device get connected to internet the save would fail — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#149>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4CPXV7XA7LNTRLZTJ2PZ3QFZ2YNANCNFSM4HFDBAVQ> .

[monajafi]

One important thing is that after successful save the save pool should be cleared not just after gaining connectivity and saving without considering the save result, which is a behaviour in native sdks

[phillwiggins]

100% correct logic. We only clear the pool, once confirmed successfully saved. I was looking at this but in the past few months been too busy to implement.

…

On Thu, Aug 22, 2019, 13:00 Mousa Najafi ***@***.***> wrote: One important thing is that after successful save the save pool should be cleared not just after gaining connectivity and saving without considering the save result, which is a behaviour in native sdks — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#149>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4CPXRITUVEN7ICKJII3SLQFZ5V3ANCNFSM4HFDBAVQ> .

[cadaniel]

Would love to see this feature. It's basically all I'm missing from what I need to replace firebase in my app (hopefully before launching)

Is there some engineering docs for this that I could help contribute?

[RodrigoSMarques]

The project is using SEMBAST which is also a NoSQL database written in Dart.
The sample application is using SEMBAST to do some offline resources. Take a look at the sample project.

You can study the source of Parse SDK on Android to see how it works. This is how I contributed to this plugin.

[Sun3]

I also would love to see saveEventually implemented for both Android and iOS.

[allanwolski]

It's very important to have offline support for our application.

[prasantco]

It's very important to have offline support for our application.

I agreed

[paulocagol]

Hello, any progress?

[RodrigoSMarques]

No progress.