NAOSDK services need ressources for the SDK to provide users with a location. The services inputs (e.g. positioning database) can either be stored in your application assets or downloaded from NAO Cloud at runtime in a synchronization step. You can be notified of the synchronization result with a NAOSyncListener on Android or a NAOSyncDelegate on iOS.
This page shows the different available synchronization method.
public void synchronizeData(final NAOSyncListener listener)
(void)synchronizeData:(id<NAOSyncDelegate>)delegate;
Go to ‘Developer’ → ‘API Keys’ and click on your current apikey
You can now ‘Edit’ to configure the period in seconds
The application must do a first synchronization to retrieve the configuration file, and each time the location service is started, the synchronization will automatically run with the period configured in the apikey.
NAOSDK has a multisite mode, that works by combining several NAOCloud sites ressources under the same Apikey.
Using the standard synchronization with a multisite Apikey will download all the related ressources of all sites.
This can be an issue when the ressources total size is large.
public void synchronizeData(final NAOSyncListener listener, final ArrayList<String> siteIdsList)
(void)synchronizeData:(id<NAOSyncDelegate>)delegate forSites:(NSArray*)siteIds;
public void synchronizeData(final NAOSyncListener listener, final Boolean auto)
(void)synchronizeData:(id<NAOSyncDelegate>)delegate withAutoSync:(bool)autoSync;