What's new
Fixed: a maxRetries below 1 could crash your app
SpendOwlConfiguration accepted any Int for maxRetries without checking it:
0stopped the SDK sending anything at all, and reported a network failure that had never been attempted- a negative value crashed the host app:
Fatal error: Range requires lowerBound <= upperBound
Values below 1 now clamp to 1. If you were passing one of them, requests that used to be dropped are now sent once. Valid configurations are unaffected, and the public API is unchanged.
Clarified: maxRetries counts attempts, not retries
It always did — only the documentation was wrong. The default of 3 means one request plus two retries, and maxRetries: 1 means a single try with no retry.
The parameter keeps its name. Renaming it would break every integration that passes the label, which is a poor trade against a doc comment; the doc comments now state the actual meaning instead.
Upgrading
Drop-in. Nothing to change unless you were passing maxRetries below 1, in which case the SDK now works rather than failing silently or crashing.
Full changelog: v1.4.1...v1.4.2