The standard ObjectBox (database) library does not include an ObjectBox Sync implementation. Depending on the programming language, it will include the Sync API, but not the implementation. For example, ObjectBox Java in its standard version allows compiling using the Sync API, but will not provide any Sync logic due to the missing implementation.
If you have not used ObjectBox before, please also be aware of documentation for the standard (non-sync) edition of ObjectBox (the ObjectBox DB) for your programming language (, , , ). You are currently looking at the documentation specific to ObjectBox Sync, which does not cover ObjectBox basics.
It is assumed that you have been in contact with the ObjectBox team and have access to Sync Server and potentially a special Sync Client version. For some platforms, we maintain packages that you can include as dependencies.
Follow the page instructions. Then change the applied Gradle plugin to the sync variant:
// This automatically adds the native dependency:
apply plugin: "io.objectbox.sync" // instead of "io.objectbox"
This will automatically add the Sync variant of the required JNI library for your platform.
If needed, e.g. to publish a JVM app that supports multiple platforms or to add Linux ARM support, add the libraries manually:
// Android
implementation("io.objectbox:objectbox-sync-android:$objectboxVersion")
// JVM
implementation("io.objectbox:objectbox-sync-linux:$objectboxVersion")
implementation("io.objectbox:objectbox-sync-macos:$objectboxVersion")
implementation("io.objectbox:objectbox-sync-windows:$objectboxVersion")
// JVM Linux on ARM (not added automatically)
implementation("io.objectbox:objectbox-sync-linux-arm64:$objectboxVersion")
implementation("io.objectbox:objectbox-sync-linux-armv7:$objectboxVersion")
This gives you specific information about how to get the Sync-enabled version of ObjectBox. Please also check our docs for in-depth information.
We may distribute ObjectBox Sync for Swift in our Cocoapods staging repository (details will be provided by the ObjectBox team). In that case, these are some typical lines to put in your Podfile (please check the version, there might be a newer one available):
target 'MyCoolSyncProject' do
use_frameworks!
pod 'ObjectBox', '4.0.0-sync'
end
import io.objectbox.sync.Sync
val syncAvailable = if (Sync.isAvailable()) "available" else "unavailable"
Log.d(App.TAG, "ObjectBox Sync is $syncAvailable")
let isSyncAvailable = Sync.isAvailable()
print("ObjectBox Sync is \(isSyncAvailable ? "available" : "unavailable")")
final isSyncAvailable = Sync.isAvailable();
print('ObjectBox Sync is ${isSyncAvailable ? "available" : "unavailable"}');
import "fmt"
import "github.com/objectbox/objectbox-go/objectbox"
// ...
var syncAvailable = "unavailable"
if objectbox.SyncIsAvailable() {
syncAvailable = "available"
}
fmt.Printf("ObjectBox Sync is %s\n", syncAvailable)
// Depending on the platform something like:
// bool isAvailable = Sync.isAvailable();
// print("ObjectBox Sync is " + (isAvailable ? "available" : "unavailable"));
Enable your Objects for ObjectBox Sync
ObjectBox Sync allows you to define which objects are synced and which are not. This is done at an object type level (a "class" in many programming languages). By default, an object (type) is local only: objects are kept in the database on the local device and do not get synced to other devices.
To enable sync for an object type, you add a "sync" annotation to the type definition. This is typically the entity source file, or, if you are using ObjectBox Generator, the FlatBuffers schema file:
@Sync
@Entity
public class User {
// ...
}
@Sync
@Entity
data class User(
// ...
)
// objectbox: sync
class User: Entity {
// ...
}
@Entity
@Sync
class User {
// ...
}
/// objectbox: sync
table User {
// ...
}
// `objectbox:"sync"`
type User struct {
// ...
}
Once the sync annotation is set on the intended types, you need to rebuild (e.g. Java/Kotlin) or trigger the ObjectBox generator (e.g. C and C++). This activates a "sync flag" in the metamodel (e.g. the model JSON file is updated).
At this point, it is not allowed to change a non-synced object type to a synced one. This would raise questions on how to handle pre-existing data, e.g. should it be deleted, synced (how exactly? using how many transactions? ...), or kept locally until objects are put again? We welcome your input on your use case if this is a scenario you encounter.
Additionally, there may only be relations between sync-enabled or non-sync entities, not across this boundary.
If you already have a non-synced type that you now want to sync (see also the info box above), these are the typical options you have:
If you are still in development, add the sync annotation and wipe your database(s) to start fresh with that new data model.
"Replace" the entity type using a new UID (check schema changes docs for the ObjectBox binding you are using). You can keep the type name; to ObjectBox it will be a different type as the UID is different. This will delete all existing data in that type.
Have a second, synced, object type and migrate your data in your code following your rules.
Start the Sync Client
Create a Sync client for your Store and start it. It connects to a given sync server URL using some form of credentials to authenticate with the server. A minimal setup can look like this:
SyncClient syncClient = Sync.client(
boxStore,
"ws://127.0.0.1" /* Use wss for encrypted traffic. */,
SyncCredentials.none()
).buildAndStart(); // Connect and start syncing.
val syncClient = Sync.client(
boxStore,
"ws://127.0.0.1" /* Use wss for encrypted traffic. */,
SyncCredentials.none()
).buildAndStart() // Connect and start syncing.
final syncClient = Sync.client(
store,
'ws://127.0.0.1:9999', // wss for SSL, ws for unencrypted traffic
SyncCredentials.none());
syncClient.start(); // connect and start syncing
std::shared_ptr<obx::SyncClient> syncClient = obx::Sync::client(
store,
"ws://127.0.0.1:9999", // wss for SSL, ws for unencrypted traffic
obx::SyncCredentials::none()
);
syncClient->start(); // connect and start syncing
OBX_sync* sync_client = obx_sync(store, "ws://127.0.0.1:9999"); // wss for SSL
obx_sync_credentials(sync_client, OBXSyncCredentialsType_NONE, NULL, 0);
obx_sync_start(sync_client); // connect and start syncing
syncClient, err := objectbox.NewSyncClient(
store,
"ws://127.0.0.1", // wss for SSL, ws for unencrypted traffic
objectbox.SyncCredentialsNone())
if err == nil { // Corrected: check if err is nil before starting
err = syncClient.Start() // Connect and start syncing.
}
if err != nil {
// Handle error, e.g., log it
fmt.Printf("Error starting sync client: %v\n", err)
}
The example uses ws://127.0.0.1 for the server endpoint. This is the IP address of localhost and assumes that you run the server and client(s) on the same machine. If it is separate machines, you need to exchange 127.0.0.1 with a reachable IP address of the server, or some valid DNS name.
Sync client is started by calling start() or buildAndStart(). It will then try to connect to the server, authenticate and start syncing. Read below for more configuration options you can use before starting the connection.
The client will now also push changes to the server for each Store transaction.
Should the client get disconnected, e.g. due to internet connection issues, it will automatically try to reconnect using an exponential back-off. Once the connection succeeds, data synchronization resumes.
Always close the client before closing the store. Closing the store with a still running sync client results in undefined behavior (e.g. crashes). Keep in mind that it typically is fine to leave the sync client and store open; once the application exits, they will be automatically closed properly.
Drop-off, send-only clients
For some use cases, a client should only report data and thus only send updates without ever receiving any data. We call those "drop-off clients". Technically, from an API perspective, these clients do not request updates from the server. Because requesting updates is the default, the sync client API has to be configured to do "manual" updates to actually disable updates from the server. This configuration has to happen before the client starts.
// C++; create syncClient as above, but do not start() just yet
syncClient->setRequestUpdatesMode(OBXRequestUpdatesMode_MANUAL);
syncClient->start();
Secure Connection
When using wss as the protocol in the server URL a TLS encrypted connection is established. Use ws instead to turn off transport encryption (insecure, not recommended; e.g. only use for testing).
Authentication options
There are currently multiple supported options for authenticating clients with a Sync server.
JWT authentication
String idToken = "<your_jwt_id_token>"; // Get from JWT authentication provider
SyncCredentials credential = SyncCredentials.jwtIdToken(idToken);
// Options for other types of JWT are available:
// jwtAccessToken(token), jwtRefreshToken(token), jwtCustomToken(token)
val idToken: String = "<your_jwt_id_token>" // Get from JWT authentication provider
val credential = SyncCredentials.jwtIdToken(idToken)
// Options for other types of JWT are available:
// jwtAccessToken(token), jwtRefreshToken(token), jwtCustomToken(token)
let idToken: String = "<your_jwt_id_token>" // Get from JWT authentication provider
let credential = SyncCredentials.makeJwtIdToken(idToken)
// Options for other types of JWT are available:
// makeJwtAccessToken(...), makeJwtRefreshToken(...), makeJwtCustomToken(...)
String idToken = "<your_jwt_id_token>"; // Get from JWT authentication provider
SyncCredentials credential = SyncCredentials.jwtIdToken(idToken);
// Options for other types of JWT are available:
// jwtAccessToken(token), jwtRefreshToken(token), jwtCustomToken(token)
std::string idToken = "<your_jwt_id_token>"; // Get from JWT authentication provider
obx::SyncCredentials credential = obx::SyncCredentials::jwtIdToken(idToken);
// Options for other types of JWT are available:
// obx::SyncCredentials::jwtAccessToken(token), obx::SyncCredentials::jwtRefreshToken(token), obx::SyncCredentials::jwtCustomToken(token)
const char* idToken = "<your_jwt_id_token>"; // Get from JWT authentication provider
// Assuming obx_sync_credentials_jwt_id_token exists or similar mechanism
obx_sync_credentials_jwt(sync_client, OBXSyncJwtTokenType_ID_TOKEN, idToken, strlen(idToken));
// Other token types would use different OBXSyncJwtTokenType enum values.
// The exact C API for JWT might vary; consult specific C API docs or headers.
idToken := "<your_jwt_id_token>" // Get from JWT authentication provider
credential := objectbox.SyncCredentialsJwtId([]byte(idToken))
Shared secret
This can be any pre-shared secret string or a byte sequence.
val credential = SyncCredentials.sharedSecret("<your_secret>")
let credential = SyncCredentials.makeSharedSecret("<your_secret>")
// use a string
final credential = SyncCredentials.sharedSecretString("<your_secret>");
// or a byte vector
final secret = Uint8List.fromList([0, 46, 79, 193, 185, 65, 73, 239, 15, 5]);
final credentialBytes = SyncCredentials.sharedSecretUint8List(secret);
// use a string
obx::SyncCredentials cred = obx::SyncCredentials::sharedSecret("your_secret_string");
// or a byte vector
std::vector<uint8_t> secret = {0, 46, 79, 193, 185, 65, 73, 239, 15, 5, 189, 186};
obx::SyncCredentials cred = obx::SyncCredentials::sharedSecret(std::move(secret));
// use a string
const char* secretStr = "your_secret_string";
obx_sync_credentials(sync_client,
OBXSyncCredentialsType_SHARED_SECRET,
secretStr,
strlen(secretStr)
);
// or a byte vector
uint8_t secretBytes[] = {0, 46, 79, 193, 185, 65, 73, 239, 15, 5, 189, 186};
obx_sync_credentials(sync_client,
OBXSyncCredentialsType_SHARED_SECRET,
secretBytes,
sizeof(secretBytes)
);
// use a string
credStr := objectbox.SyncCredentialsSharedSecret([]byte("your_secret_string"))
// or a byte vector
secretBytes := []byte{0, 46, 79, 193, 185, 65, 73, 239, 15, 5, 189, 186}
credBytes := objectbox.SyncCredentialsSharedSecret(secretBytes)
// use a string
var cred = objectbox.SyncCredentialsGoogleAuth([]byte("string"))
// or a byte vector
var secret = []byte{0, 46, 79, 193, 185, 65, 73, 239, 15, 5, 189, 186}
var cred = objectbox.SyncCredentialsGoogleAuth(secret)
No authentication (insecure)
Never use this option in an app shipped to customers. It is inherently insecure and allows anyone to connect to the sync server.
For development and testing, it is often easier to just have no authentication at all to quickly get things up and running.
Using the example above, the sync client automatically connects to the server and starts to sync. It is also possible to just build the client and then start to sync once your code is ready to.
// Just build the client.
SyncClient syncClient = Sync.client(...).build();
// Start now.
syncClient.start();
// Just build the client.
val syncClient = Sync.client(...).build()
// Start now.
syncClient.start()
Note that a started sync client can not be started again. Stop and close an existing one and build a new one instead.
Listening to events
The sync client supports listening to various events, e.g. if authentication has failed or if the client was disconnected from the server. This enables other components of an app, like the user interface, to react accordingly.
It's possible to set one or more specific listeners that observe some events, or a general listener that observes all events. When building a Sync client use:
loginListener(listener) to observe login events.
completedListener(listener) to observe when synchronization has completed.
connectionListener(listener) to observe connection events.
listener(listener) to observe all of the above events. Use AbstractSyncListener and only override methods of interest to simplify your listener implementation.
See the description of each listener class and its methods for details.
Note that listeners can also be set or removed at any later point using SyncClient.setSyncListener(listener) and related methods.
SyncLoginListener loginListener = new SyncLoginListener() {
@Override
public void onLoggedIn() {
// Login succesful.
}
@Override
public void onLoginFailed(long syncLoginCode) {
// Login failed. Returns one of SyncLoginCodes.
}
};
SyncCompletedListener completedListener = new SyncCompletedListener() {
@Override
public void onUpdatesCompleted() {
// A sync has completed, client is up-to-date.
}
};
SyncConnectionListener connectListener = new SyncConnectionListener() {
@Override
public void onDisconnected() {
// Client disconnected from the server.
// Depending on the configuration it will try to re-connect.
}
};
// Set listeners when building the client.
SyncClient syncClient = Sync.client(...)
.loginListener(loginListener)
.completedListener(completedListener)
.connectionListener(connectListener)
.build();
// Set (or replace) a listener later.
syncClient.setSyncLoginListener(listener);
// Remove an existing listener.
syncClient.setSyncConnectionListener(null);
It's possible to set one or more specific listeners that observe some events, or a general listener that observes all events. When building a Sync client use:
loginListener(listener) to observe login events.
completedListener(listener) to observe when synchronization has completed.
connectionListener(listener) to observe connection events.
listener(listener) to observe all of the above events. Use AbstractSyncListener and only override methods of interest to simplify your listener implementation.
See the description of each listener class and its methods for details.
Note that listeners can also be set or removed at any later point using SyncClient.setSyncListener(listener) and related methods.
val loginListener: SyncLoginListener = object : SyncLoginListener {
override fun onLoggedIn() {
// Login succesful.
}
override fun onLoginFailed(syncLoginCode: Long) {
// Login failed. Returns one of SyncLoginCodes.
}
}
val completedListener = SyncCompletedListener {
// A sync has completed, client is up-to-date.
}
val connectListener = object : SyncConnectionListener {
override fun onDisconnected() {
// Client disconnected from the server.
// Depending on the configuration it will try to re-connect.
}
}
// Set listeners when building the client.
val syncClient = Sync.client(...)
.loginListener(loginListener)
.completedListener(completedListener)
.connectionListener(connectListener)
.build()
// Set (or replace) a listener later.
syncClient.setSyncLoginListener(listener)
// Remove an existing listener.
syncClient.setSyncConnectionListener(null)
It's possible to set one or more specific listeners that observe some events, or a general listener that observes all events. The SyncClient protocol offers the following properties to attach listeners:
loginListener to observe login events.
completedListener to observe when synchronization has completed.
connectionListener to observe connection events.
listener to observe all of the above events.
There is a protocol for each listener type. Note that listeners can also be set or removed at any later point by setting the listener property to nil.
By implementing a listener protocol and setting the matching property in SyncClient, you are called back. Let's have a look at the available listener protocols for details:
/// Listens to login events.
public protocol SyncLoginListener {
/// Called on a successful login.
///
/// At this point the connection to the sync destination was established and
/// entered an operational state, in which data can be sent both ways.
func loggedIn()
/// Called on a login failure with a `result` code specifying the issue.
func loginFailed(result: SyncCode)
}
/// Listens to sync completed events.
public protocol SyncCompletedListener {
/// Called each time a sync was "completed", in the sense that the client
/// caught up with the current server state. The client is "up-to-date".
func updatesCompleted()
}
/// Listens to sync connection events.
public protocol SyncConnectionListener {
/// Called when connection is established; happens before an actual login
func connected()
/// Called when the client is disconnected from the sync server, e.g. due to a network error.
///
/// Depending on the configuration, the sync client typically tries to reconnect automatically,
/// triggering a `SyncLoginListener` again.
func disconnected()
}
/// Listens to all possible sync events. See each protocol for detailed information.
public protocol SyncListener: SyncLoginListener, SyncCompletedListener, SyncChangeListener, SyncConnectionListener {
}
It's possible to listen to sync-related events on the client. Use the following SyncClient getters to connect to a stream:
Stream<SyncLoginEvent> get loginEvents - such as logged-in, credentials-rejected.
Stream<void> get completionEvents to observe when synchronization has completed.
Stream<SyncConnectionEvent> get connectionEvents to observe connection events.
Note that these streams don't buffer events so unless you're subscribed, no events are collected. Additionally, don't forget to cancel the subscription when you don't care about the information anymore, to free up resources.
final client = Sync.client(...);
final subscription = client.loginEvents.listen((SycnLoginEvent event) {
if (event == SyncLoginEvent.loggedIn) print('Logged in successfully');
});
client.start();
...
// don't forget unsubscribe if you don't care about the events anymore
subscription.cancel();
struct LoginListener : public obx::SyncClientLoginListener {
void loggedIn() noexcept override;
void loginFailed(OBXSyncCode code) noexcept override;
};
auto loginListener = std::make_shared<LoginListener>();
syncClient->setLoginListener(loginListener);
// there can be only one listener of a given type, so calling again with a
// different callback changes the listener (un-assigns the previous one)
syncClient->setLoginListener(...);
// reset (remove) a listener
syncClient->setLoginListener(nullptr);
void login_listener(void* arg) {
(*(int*) arg)++;
}
void main() {
...
int login_listener_arg = 0;
obx_sync_listener_login(sync_client, login_listener, &login_listener_arg);
}
// there can be only one listener of a given type, so calling again with a
// different callback changes the listener (un-assigns the previous one)
obx_sync_listener_login(sync_client, ..., ...);
// reset (remove) a listener
obx_sync_listener_login(sync_client, NULL, NULL);
syncClient.SetLoginListener(func() { println("Logged-in") })
// there can be only one listener of a given type, so calling again with a
// different callback changes the listener (un-assigns the previous one)
syncClient.SetLoginListener(func() { ... })
// reset (remove) a listener
syncClient.SetLoginListener(nil)
Advanced
Listening to incoming data changes
For advanced use cases, it might be useful to know exactly which objects have changed during an incoming sync update. This is typically not necessary, as observing a box or a query may be easier.
On each sync update received on the client, the listener is called with an array of "Sync Change" objects, one for each affected entity type. It includes a list of affected object IDs - the ones that were put or removed in the incoming update.
Use changeListener(changeListener) when building the client and pass a SyncChangeListener to receive detailed information for each sync update. Or set or remove it at any later point using SyncClient.setSyncChangeListener(changeListener).
SyncChangeListener changeListener = syncChanges -> {
for (SyncChange syncChange : syncChanges) {
// This is equal to Example_.__ENTITY_ID.
long entityId = syncChange.getEntityTypeId();
// The @Id values of changed and removed entities.
long[] changed = syncChange.getChangedIds();
long[] removed = syncChange.getRemovedIds();
}
};
// Set the listener when building the client.
syncBuilder.changeListener(changeListener);
// Or set the listener later.
syncClient.setSyncChangeListener(changeListener);
// Calling again replaces an existing listener.
syncClient.setSyncChangeListener(changeListener);
// Remove an existing listener.
syncClient.setSyncChangeListener(null);
Use changeListener(changeListener) when building the client and pass a SyncChangeListener to receive detailed information for each sync update. Or set or remove it at any later point using SyncClient.setSyncChangeListener(changeListener).
val changeListener = SyncChangeListener { syncChanges ->
for (syncChange in syncChanges) {
// This is equal to Example_.__ENTITY_ID.
val entityId = syncChange.entityTypeId
// The @Id values of changed and removed entities.
val changed = syncChange.changedIds
val removed = syncChange.removedIds
}
}
// Set the listener when building the client.
syncBuilder.changeListener(changeListener)
// Or set the listener later.
syncClient.setSyncChangeListener(changeListener)
// Calling again replaces an existing listener.
syncClient.setSyncChangeListener(changeListener)
// Remove an existing listener.
syncClient.setSyncChangeListener(null)
Coming soon!
Use Stream<List<SyncChange>> get changeEvents on the SyncClient to receive detailed information for each sync update. Make sure to cancel the subscription when you don't need the information anymore to clear up resources.
final subscription = client.changeEvents
.listen((List<SyncChange> event) => event.forEach((change) {
print('${change.entity}(${change.entityId}) '
'puts=${change.puts} removals=${change.removals}');
}));
...
// don't forget unsubscribe if you don't care about the events anymore
subscription.cancel();
/// Sample listener collecting all puts and removals
class StatsCollector {
struct EntityChanges {
std::vector<obx_id> puts;
std::vector<obx_id> removals;
};
std::unordered_map<obx_schema_id, EntityChanges> statsPerEntity;
/// Receives changes on the object instance, forwarded by the static forward().
void onChanges(const OBX_sync_change_array* changes) {
for (size_t i = 0; i < changes->count; i++) {
const OBX_sync_change& change = changes->list[i];
EntityChanges& stats = statsPerEntity[change.entity_id];
if (change.puts) collect(change.puts, stats.puts);
if (change.removals) collect(change.puts, stats.removals);
}
}
/// Update given vector by adding all ids from current change list.
void collect(const OBX_id_array* ids, std::vector<obx_id>& targetVector) {
targetVector.reserve(targetVector.size() + ids->count);
for (size_t i = 0; i < ids->count; i++) {
targetVector.push_back(ids->ids[i]);
}
}
public:
/// Just forwards the C-callback to the instance of this class.
static void forward(void* arg, const OBX_sync_change_array* changes) {
static_cast<StatsCollector*>(arg)->onChanges(changes);
}
};
void main() {
...
StatsCollector collector;
syncClient->setChangeListener(StatsCollector::forward, &collector);
}
syncClient.SetChangeListener(func(changes []*objectbox.SyncChange) {
fmt.Printf("received %d changes\n", len(changes))
for i, change := range changes {
fmt.Printf("change %d: %v\n", i, change)
// change.EntityId is a "model-entity-id", e.g. we can choose to process
// only changes on Entity `User`, with the generated `UserBinding`:
if change.EntityId == model.UserBinding.Id {
fmt.Printf("put user IDs %v\n", change.Puts)
fmt.Printf("deleted user IDs %v\n", change.Removals)
}
}
})
Listeners concurrency
Some events may be issued in parallel, from multiple background threads. To help you understand when and how you need to take care of concurrency (e.g. use mutex/atomic variables), we've grouped the sync listeners to these two groups:
There can be only one event executed at any single moment from a listener in a single group. You can imagine this as if there were two parallel threads, one could only issue "state" events, the other only "data change" events.
Controlling sync updates behavior
By default, after the Sync client is logged in, its database is updated from the server and the client will automatically subscribe for any future changes. For advanced use cases, like unit testing, it is possible to control when the client receives data updates from the server.
To change the default behavior, configure the "Request Updates Mode" before starting the client connection. Three modes are available:
automatic (default): receives updates on login and subscribes for future updates.
automatic, but no pushes: receives updates on login but doesn't subscribe for future updates.
manual: no automatic updates on login or on any updates in the future.
When using one of the non-default modes, synchronization can be controlled after login during application runtime by requesting and cancelling updates using the client:
SyncClient syncClient = syncBuilder
// Turn off automatic sync updates.
.requestUpdatesMode(RequestUpdatesMode.MANUAL)
.build();
// Wait for login attempt, proceed if logged in.
syncClient.awaitFirstLogin(20 * 1000 /* ms */);
if (syncClient.isLoggedIn()) {
// Turn on automatic sync updates.
syncClient.requestUpdates();
// Turn off automatic sync updates, cancel ongoing sync.
syncClient.cancelUpdates();
// Request one-time update.
// Will update client with latest data.
syncClient.requestUpdatesOnce();
}
val syncClient = syncBuilder
// Turn off automatic sync updates.
.requestUpdatesMode(RequestUpdatesMode.MANUAL)
.build()
// Wait for login attempt, proceed if logged in.
syncClient.awaitFirstLogin(20 * 1000 /* ms */)
if (syncClient.isLoggedIn()) {
// Turn on automatic sync updates.
syncClient.requestUpdates()
// Turn off automatic sync updates, cancel ongoing sync.
syncClient.cancelUpdates()
// Request one-time update.
// Will update client with latest data.
syncClient.requestUpdatesOnce()
}
Coming soon!
final client = Sync.client(...);
client.setRequestUpdatesMode(SyncRequestUpdatesMode.manual);
client.start(); // Connect but don't synchronize yet.
// Turn on sync updates and subscribe for pushes.
client.requestUpdates(subscribeForFuturePushes: true);
// Cancel ongoing synchronization & unsubscribe from future updates.
client.cancelUpdates();
// Alternatively, catch up with the server but don't subscribe for future.
// You can call this instead of subscribing to do one-time updates as needed.
client.requestUpdates(subscribeForFuturePushes: false);
std::shared_ptr<obx::SyncClient> syncClient = obx::Sync::client(store, ...);
syncClient->setRequestUpdatesMode(OBXRequestUpdatesMode_MANUAL);
syncClient->start(); // Connect but don't synchronize yet.
// Turn on sync updates and subscribe for pushes.
syncClient->requestUpdates(true);
// Cancel ongoing synchronization & unsubscribe from future updates.
syncClient->cancelUpdates();
// Alternatively, catch up with the server but don't subscribe for future.
// You can call this instead of subscribing to do one-time updates as needed.
syncClient->requestUpdates(false);
OBX_sync* sync_client = obx_sync(store, ...);
obx_sync_credentials(sync_client, ...);
obx_sync_request_updates_mode(sync_client, OBXRequestUpdatesMode_MANUAL);
obx_sync_start(sync_client); // Connect but don't synchronize yet.
// Turn on sync updates and subscribe for pushes.
obx_sync_updates_request(sync_client, true);
// Cancel ongoing synchronization & unsubscribe from future updates.
obx_sync_updates_cancel(sync_client);
// Alternatively, catch up with the server but don't subscribe for future.
// You can call this instead of subscribing to do one-time updates as needed.
obx_sync_updates_request(sync_client, false);
syncClient, err := objectbox.NewSyncClient(...)
syncClient.SetRequestUpdatesMode(objectbox.SyncRequestUpdatesManual)
syncClient.Start() // Connect but don't synchronize yet.
// Turn on sync updates and subscribe for pushes.
syncClient.RequestUpdates(true)
// Cancel ongoing synchronization & unsubscribe from future updates.
syncClient.CancelUpdates()
// Alternatively, catch up with the server but don't subscribe for future.
// You can call this instead of subscribing to do one-time updates as needed.
syncClient->requestUpdates(false)
See the instructions for Flutter or Dart and note the different instructions for Sync (different Flutter library, increasing Android minSdkVersion, install script parameter).
Or use to get ObjectBox headers and library ready to use in your project:
Using Android emulator? You can use 10.0.2.2 to reach the host (the machine running the emulator).
Once the client is logged in, the server will push any changes it has missed. The server will also push any future changes while the client remains connected. This can be configured.
All of this happens asynchronously. To observe these events (log in, sync completed, …) read below on how to .
Clients can be authenticated using tokens in JWT (JSON web token) format. The general process is outlined in the . Your client application typically will use a JWT authentication provider SDK to get a token in JWT format. This token is then set as a credential using the ObjectBox Sync client API:
The ObjectBox Sync server supports authenticating users using their Google account. This assumes is integrated into your app and it has .
- listening to login success/failure, connection status, sync complete.
