Configuration of WASTransporter and WASProcessor
When you create an instance of WASTransporter or WASProcessor, you need to provide a configuration object of type WASTransporterConfig.
To encrypt and decrypt the data, the library generates a unique fingerprint calculated from device-specific data, such as battery level, operating system version, and similar data.
Activation Spawn is using this generator to safely transfer the activation data between applications.
In addition, static data additionalData of your choosing is added to the calculation.
It’s crucial that the Source App and Target App are using the same static additional data when initializing WASTransporter and WASProcessor.
Configuration option
You can choose from the following options:
-
WASTransporterConfig.stable: Transporter will use a stable time-based but still predictable fingerprint. This configuration is good if you expect that the transfer will take more than just seconds.
-
WASTransporterConfig.semiStable: Transporter will use a semi-stable time-based but still predictable fingerprint. This configuration is good if you expect that the transfer will take seconds (for example, 10).
-
WASTransporterConfig.unstable: Transporter will use an unstable time-based fingerprint. Fingerprint for the transport can change anytime, so use this in scenarios where the expected transfer takes no longer than a few seconds.
Each configuration takes 2 parameters:
sameTeam: boolean: Iftrue, then the generator will be specific for an application vendor (same Apple team/same Android ID).validityInSeconds: number: If set, then the fingerprint will be valid for a given number of seconds.