Skip to content

v1.10.0

Latest

Choose a tag to compare

@cemardafil cemardafil released this 18 Nov 04:22
f78f7c2

Provider context sized by bytes, calls in call order

New (backwards-compatible):

  • setProviderContext is bounded by size, not count (#72). No limit on providers or keys; 2 KiB per value and 16 KiB for the whole map you set (encoded JSON, names included), up from 10 providers × 10 keys × 256 B. Fits hybrid apps forwarding ~20 providers and encrypted enrichment envelopes.
    • A write that would grow the map past 16 KiB is rejected (false, warning, prior values kept). Overwriting with a same-size or smaller value, or removing one, always works, so a map saved under the old limits can still shrink.
    • Sizes are counted the same way as on Android.

Fixes — changes you may notice:

  • Back-to-back calls run in call order (#73). Each call used to run in its own task, so identify("u1"); track("Purchase") could ship the track without the userId, and calls made before initialize could replay out of order. Static reset() now unbinds immediately, so a call on the next line no longer reaches the discarded client.
  • Stored userId / groupId / advertisingId are read before initialization finishes (#73). The first event after launch could go out with userId missing.
  • Slashes go out unescaped (#74), as Android sends them: https://… instead of https:\/\/…. Same JSON value; smaller bodies for events with URLs or base64.

PRs: #72, #73, #74 · bump #75

Full Changelog: v1.9.0...v1.10.0