Configuration of the Transporter

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 uses this generator to safely transfer the activation data between applications.

In addition, static data additionaData 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 Transporter and Processor.

Configuration option

You can choose from the following options:

  • TransporterConfig.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.

  • TransporterConfig.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).

  • TransporterConfig.unstable: Transporter will use an unstable time-based fingerprint. Fingerprint for the transport can change anytime so use this in scenarios where expected transfer takes no longer than a few seconds.

Each configuration takes 2 parameters:

  • sameTeam: Boolean: If true then the generator will be specific for an application vendor (same Android ID).
  • validityInSeconds: Long: If set, then the fingerprint will be valid for a given amount of seconds.
Last updated on Jun 06, 2024 (09:34) Edit on Github Send Feedback
Search

develop

Activation Spawn SDK for Android