Release 9.10.0

[SpertsyanKM]

Release PR

New

• Swift Package Manager support for iOS. Editor/QonversionDependencies.xml now declares the native QonversionSandwich as a Swift package (https://github.com/qonversion/sandwich-sdk.git, exact 7.13.0) next to the CocoaPod. With External Dependency Manager for Unity (EDM4U) 1.2.189+ on Unity 2021.3+ and Swift Package Manager Integration enabled in Assets → External Dependency Manager → iOS Resolver → Settings (the default), the package is linked into UnityFramework and the pod is left out of the generated Podfile — no action needed. Older EDM4U, Unity older than 2021.3 or SPM integration turned off keep installing the QonversionSandwich CocoaPod exactly as before. Resolves Unity SDK not compatible with new qonversion-ios-sdk (SPM) – QonversionSandwich module missing qonversion-ios-sdk#643 (Swift Package Manager support for iOS via EDM4U (CocoaPods kept as fallback), sandwich 7.13.0 #329).

Improvements & fixes

• Native iOS SDK updated via QonversionSandwich 7.13.0: iOS 6.15.0 — public PromotionalOffer(productDiscount:paymentDiscount:) initializer, QONErrors.isAuthorizationError, fixed Swift Package Manager build for tvOS. Android stays on 9.7.0 (Swift Package Manager support for iOS via EDM4U (CocoaPods kept as fallback), sandwich 7.13.0 #329).

Breaking notes & requirements

• Swift Package Manager path requirements: Unity 2021.3+, EDM4U 1.2.189+ (com.google.external-dependency-manager from OpenUPM or the .unitypackage from EDM4U's GitHub releases — Google's UPM registry is no longer available), Xcode 15+, iOS deployment target 13.0+ (unchanged), github.com reachable from the build machine. To stay on CocoaPods, turn off Swift Package Manager Integration in the iOS Resolver settings.
• Do not combine EDM4U 1.2.187 / 1.2.188 with Unity older than 2021.3: those versions drop the pod when a Swift package is declared without adding the package (fixed in EDM4U 1.2.189). Update EDM4U or turn Swift Package Manager Integration off.
• If your project adds the native iOS SDK itself — a Qonversion pod in your own *Dependencies.xml or Podfile, or a qonversion-ios-sdk Swift package (for example as a workaround for ios#643) — remove it: the sandwich package depends on qonversion-ios-sdk exactly 6.15.0, a second copy produces duplicate symbols or a package resolution conflict. On the CocoaPods path the previous rule still applies: apps that also declare the Qonversion pod must move to 6.15.0.
• With default EDM4U settings a (now empty) Podfile is still generated and pod install still runs, so CocoaPods must still be installed and Unity-iPhone.xcworkspace is still produced. If Qonversion is your only pod, turn off Allow empty Podfile generation in the iOS Resolver settings to skip CocoaPods entirely — then open and build Unity-iPhone.xcodeproj instead of the workspace.
• CocoaPods trunk becomes read-only on December 2, 2026. The QonversionSandwich CocoaPod remains available as a fallback, but plan to move to the Swift Package Manager path before then.

Summary by CodeRabbit

• Chores
  • Updated the SDK version to 9.10.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: qonversion/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: c5d8bb0d-f192-43f2-969e-312744c4201f

📥 Commits

Reviewing files that changed from the base of the PR and between 9fef214 and ba5aac1.

📒 Files selected for processing (2)

• Runtime/Scripts/Internal/QonversionInternal.cs
• package.json

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• qonversion/go-micro (manual)

Included review availability: 8 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour.

---

📝 Walkthrough

Walkthrough

The package metadata and internal Unity SDK version reported to native wrappers are updated from 9.9.0 to 9.10.0.

Changes

SDK Version Alignment

Layer / File(s)	Summary
Version metadata and runtime reporting package.json, Runtime/Scripts/Internal/QonversionInternal.cs	The package version and SdkVersion value are updated from 9.9.0 to 9.10.0.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to ba5aa

This version-alignment change presents no identified merge-blocking risk.

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore (reviewers only)

❌ Failed checks (1 error, 3 warnings)

Check name	Status	Explanation	Resolution
Rollout And Recovery Evidence	❌ Error	This release PR activates an automatic public release path without bounded rollout evidence. The reviewed diff changes the package version and the runtime-reported SDK version to 9.10.0. GitHub identi…	Before merge, add a release plan and enforce it as a merge gate. Define concrete verification results for the 9.10.0 artifact, including the supported Unity/iOS SPM, CocoaPods fallback, and Android paths. Define the activation order from me…
Title check	⚠️ Warning	The title identifies the release version but does not name the affected product or system area, or the behavioral outcome. The changes affect the Unity SDK and add or update release integration behavi…	Update the title to name the affected area and outcome, such as "Unity SDK 9.10.0: Add iOS Swift Package Manager support".
Linked Issues check	⚠️ Warning	Issue #643 requires a Unity iOS integration path that builds with the new SPM-based SDK. The reviewed bridge files still use @import QonversionSandwich, QonversionSandwich, SandwichError, and re…	Implement the SPM-compatible iOS bridge and dependency configuration for the Unity package. Retain the CocoaPods path where required. Add automated coverage that verifies an SPM-based Unity iOS build and the bridge types used by the project…
Out of Scope Changes check	⚠️ Warning	The reviewed changes update only the Unity SDK version from 9.9.0 to 9.10.0 in QonversionInternal.cs and package.json. These version-only changes do not connect to the coding objective in issu…	Remove the unrelated version-only changes from the issue-scoped change set, or include them only with the SPM bridge and dependency changes that make the version release the delivery of issue #643.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Behavior And Regression Safety	✅ Passed	PASS. The reviewed range changes only the package version and the SdkVersion passed by QonversionInternal.InitializeInstance to StoreSdkInfo, from 9.9.0 to 9.10.0. Both values match. The SPM…
Security And Tenant Isolation	✅ Passed	PASS. The reviewed range changes only the package version and the SDK version metadata from 9.9.0 to 9.10.0. The metadata flows to StoreSdkInfo and does not alter authentication, authorization, tenant…
Contract And Data Compatibility	✅ Passed	PASS. The review-scoped diff contains only two literal version updates: package.json changes 9.9.0 to 9.10.0, and the private SdkVersion constant changes to 9.10.0. The existing `StoreSdkInf…

Full details: Title check

Explanation

The title identifies the release version but does not name the affected product or system area, or the behavioral outcome. The changes affect the Unity SDK and add or update release integration behavior.

Full details: Linked Issues check

Explanation

Issue #643 requires a Unity iOS integration path that builds with the new SPM-based SDK. The reviewed bridge files still use @import QonversionSandwich, QonversionSandwich, SandwichError, and related Sandwich types in QonversionBridge.m, UtilityBridge.h, NoCodesBridge.m, and QNUNoCodesDelegate.h. The available change summary lists only version updates in QonversionInternal.cs and package.json. Those changes do not implement SPM support or provide automated build coverage.

Resolution

Implement the SPM-compatible iOS bridge and dependency configuration for the Unity package. Retain the CocoaPods path where required. Add automated coverage that verifies an SPM-based Unity iOS build and the bridge types used by the project.

Full details: Out of Scope Changes check

Explanation

The reviewed changes update only the Unity SDK version from 9.9.0 to 9.10.0 in QonversionInternal.cs and package.json. These version-only changes do not connect to the coding objective in issue #643 because they do not change the iOS bridge or SPM integration. The whole diff could not be fetched, so this assessment relies on the provided change summary and reviewed-head files; no ignored files are listed.

Full details: Rollout And Recovery Evidence

Explanation

This release PR activates an automatic public release path without bounded rollout evidence. The reviewed diff changes the package version and the runtime-reported SDK version to 9.10.0. GitHub identifies the head as release/9.10.0 with the one-click-release label, which satisfies .github/workflows/publish_release.yml when the PR merges to main. That workflow calls the shared publish workflow, which runs gh release create ... --latest against the merge commit. The PR description contains release notes and compatibility requirements, but no concrete verification criteria, activation order, stop signals, or rollback/forward-recovery procedure. The repository checks only validate the dependency XML and pin consistency; they do not bound this release activation.

Resolution

Before merge, add a release plan and enforce it as a merge gate. Define concrete verification results for the 9.10.0 artifact, including the supported Unity/iOS SPM, CocoaPods fallback, and Android paths. Define the activation order from merge to tag/GitHub release and package availability. Define stop signals and who can stop or disable the release workflow before publication. Define recovery for a bad release, including retaining the prior version for consumers, avoiding tag reuse, and issuing a forward-fix version. Do not merge while the one-click-release path lacks this evidence.

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/9.10.0

---

_{Comment @coderabbitai help to get the list of available commands.}