7.2.6

Bug Fixes

• Fixed an in-app message triggered by postEvent not being shown on a first launch while its content was still downloading
• Fixed setEmail called from a Rich Media form or via Pushwoosh.configure.setEmail(_:) not registering the email
• Fixed in-app purchase transactions not being tracked
• Fixed a blank email submitted from a Rich Media form being sent to the server
• Fixed Objective-C compile errors when calling configuration methods on [Pushwoosh configure]

Improvements

• postEvent(_:withAttributes:completion:) now calls its completion as soon as the server has accepted the event, instead of waiting for the in-app resources of the whole account to download
• An in-app triggered by postEvent now waits only for its own content to download, and the loading overlay appears only while that download is actually running
• SDK network responses and in-app content downloads are processed off the main thread, so a busy UI no longer delays them and they no longer compete with the app's rendering; SDK completion handlers still arrive on the main queue

Behaviour change. The postEvent completion means "the event was posted", the documented contract, and no longer implies that an in-app triggered by that event is ready or shown. On a first launch with an empty resource cache the callback used to take several seconds; it now takes milliseconds. The in-app itself still appears; to observe its lifecycle use the Pushwoosh.inApp delegate for native in-app messages, and PWRichMediaPresentingDelegate (richMediaManager(_:didPresentRichMedia:), richMediaManager(_:didCloseRichMedia:), richMediaManager(_:presentingDidFailForRichMedia:withError:)) for Rich Media ones. Affects wrappers that resolve a Future or a Promise from this completion: Flutter's and Capacitor's postEvent, and the postEvent bridges available to Rich Media JavaScript, whose success callback now means the event was posted rather than the resource being ready.