1.3.1

Changed: on iOS the native SDK is now a Swift package, not a CocoaPods pod. The iOS post-build step adds https://github.com/joryio/joryio-ios-sdk.git at exactly this version to the exported Xcode project and links the Joryio product into UnityFramework (and JoryioUI as well when the JORYIO_IOS_UI scripting define is set). Editor/JoryioDependencies.xml now lists only the Android artifact; External Dependency Manager is no longer involved on iOS. Upgrading from 1.3.0, which used the Joryio/Core pod: build the iOS player once with Replace rather than Append, and delete any <iosPod name="Joryio/..."> line from your own External Dependency Manager files.

Later Append builds keep the package in step: the Swift package reference is moved to the version of the installed Unity package, and JoryioUI is linked when JORYIO_IOS_UI is set after the first export. Removing the define needs a Replace build to unlink JoryioUI; the build log says so.

Added: JoryioInAppMessage.MaxWidth for HTML modals and slide-ups (null for every other message), forwarded by both native bridges. When you draw messages yourself, give your web view min(MaxWidth, screen width - your margins) before the content lays out and measure the height from document.body (with body{display:flow-root}), not the root element, whose height never drops below the web view's own.

Fixed (when the native SDK draws messages: joryio-android-ui on Android, the JORYIO_IOS_UI define on iOS): HTML in-app messages did not work on Android since 1.3.0, and native HTML modals and slide-ups could grow but never shrink. See the iOS and Android release notes.

No other C# API changes.