Qonversion Release 9.7.0

[SpertsyanKM]

Release PR

New

• New public API Qonversion.shared.invalidateRemoteConfigsCache() — invalidates the in-memory cache of remote configs so the next remoteConfig / remoteConfigList call fetches a fresh targeting evaluation. No network request itself; call it after changing user properties your targeting depends on. Not needed after identify — see below (feat: invalidateRemoteConfigsCache() + remote config refetch after same-uid identify (DEV-1236) #853).

Improvements & fixes

• identify() resolving to the same Qonversion user now invalidates the remote configs cache automatically, so the first login no longer serves the pre-login targeting evaluation for the rest of the process lifetime (feat: invalidateRemoteConfigsCache() + remote config refetch after same-uid identify (DEV-1236) #853).
• A remote config load in flight during an invalidation is re-issued so its callbacks receive a fresh evaluation; if the retry fails, the superseded evaluation is delivered instead of an error (feat: invalidateRemoteConfigsCache() + remote config refetch after same-uid identify (DEV-1236) #853).
• Bundled fallback configs are no longer cached: offline apps recover automatically when connectivity returns, and a request short-circuited by the local rate limiter still receives the bundled payload (remote configs only) (feat: invalidateRemoteConfigsCache() + remote config refetch after same-uid identify (DEV-1236) #853).
• Fixed forceSendProperties losing the send-scheduled flag after a forced flush, and user property batches now reliably reach the server before a remote config evaluation (fix: unstick property sending flag + invalidate named-key RC cache on attach/detach (DEV-1232) #852).
• Remote config cache hits now flush pending user properties, so a cache hit cannot swallow a property batch (feat: invalidateRemoteConfigsCache() + remote config refetch after same-uid identify (DEV-1236) #853).

Behavior changes

• A remoteConfig() request in flight when identify() completes resolves after two round trips instead of one (fresh-data-for-latency trade; reliability is not reduced).
• invalidateRemoteConfigsCache() is a new member of the public Qonversion interface — custom implementations of the interface must add it.