Validating Configuration Files
Configure WebSockets
REST Wrappers for SFAP APIs
Using Key-Value Stores for Secure Data Storage
Dark Mode and Dark Theme Settings
When you’re writing formally structured text files, schema validation is useful at any level. For SmartStore and Mobile Sync configuration files, schema validation is especially welcome for complex configurations that handle related records.
Beginning in Mobile SDK 8.0, you can validate your configuration files using any of the following Mobile SDK utilities:
To validate your configurations, you use the checkconfig action.
Here’s a Mobile SDK npm utility call to checkconfig.
1$ forceios checkconfigThe tool then prompts you for the following information:
configpath—Path to the configuration fileconfigtype—Type of the configuration file. Must be either ”store” or “syncs”.Here’s an sfdx call to checkconfig.
1$ sfdx mobilesdk:ios:checkconfigYou can replace ios with android, hybrid, or reactnative—in every case, though, the result is the same. You then provide the following required options:
-c, --configpath=<path to the configuration file>-y, --configtype=<either ”store” or “syncs”>If you prefer, you can use Mobile SDK schemas with third-party JSON validators. You can find the published schema definitions here:
store.schema.jsonsyncs.schema.jsonTargets of type soql now accept an optional maxBatchSize property. This property accepts any integer between 200 and 2,000. Default value is 2,000.
To overcome differences between iOS and Android syncs configuration syntax, the iOS schema was revised as follows to match Android’s syntax.
parent_children. Formerly, iOS used parentChildren.createFieldlist. Formerly, iOS used parentCreateFieldlist.updateFieldlist. Formerly, iOS used parentUpdateFieldlist.Sample configuration files:
We've Moved