[ianrumac]

Why

On iOS, a landscape-only game can be rotated to portrait while a paywall is open, and it stays in portrait after the paywall closes. A customer reported this for a map that's locked to landscape through Screen.autorotateTo*.

SuperwallKit presents the paywall in its own window. That window's root is a plain UIViewController, which allows every orientation, so Unity's orientation settings are never checked. The fix is native: superwall/Superwall-iOS#568 makes the paywall window follow the app's top view controller. For a Unity game, that's Unity's view controller, which reports Screen.autorotateTo*. When the paywall closes, the fix also asks UIKit to check orientations again.

What

• The generated Podfile now requires SuperwallKit >= 4.19.1, < 5.0. 4.19.1 is the version staged on Superwall-iOS develop, so it's the first release #568 can ship in. No bridge or C# changes are needed.
• Append builds move an existing Podfile off any requirement this package wrote before (~> 4.0 and >= 4.12.10, < 5.0). Before, only ~> 4.0 was moved. A requirement the developer set by hand is left alone. This logic is now a testable UpdateSuperwallKitRequirement.
• Old requirements are stored by their version part only, so native-sdk-bump.yml's sed on the pod 'SuperwallKit', '…' line no longer rewrites them too.
• Changelog entry under 0.4.0, which isn't tagged yet.

Before merging

• Draft until SuperwallKit 4.19.1 is released with #568 in it. #568 is still open, and its changelog entry sits under 4.18.3, which has already shipped. It needs to move to 4.19.1. If the fix ships in a different version, update the floor here. Merging earlier would make pod install fail.
• I left ci~/ios-harness/Package.swift at from: "4.12.10". Raising it before the release would break the harness's package resolution, and the harness doesn't test orientation.

Testing

• Added Tests/Editor/PodfileRequirementTests.cs: both earlier requirements get moved, the current one is unchanged, and a hand-set pin is kept. These are Editor tests, and CI doesn't run Editor tests.
• Not compiled or run locally: this was a Linux machine without Unity or .NET.
• Still needs a manual check: in a landscape-locked Unity build on a device, open a paywall, rotate the device, and confirm it stays in landscape and the game is in landscape after the paywall closes.

---

Generated by Claude Code

[maple-review-bot]

Maple review

🟡 Confidence 6/10 · needs attention. Held at 6 because a correctness warning is open.
_{1 warning −1 · tests covered · risk medium}

Raises the SuperwallKit floor to 4.19.1 and migrates two previously generated Podfile requirements. The migration needs to preserve customized constraint lists before merging.

Before merge

• Manual · Confirm SuperwallKit 4.19.1 is published with Superwall-iOS #568 before merging.
• Manual · Run the Unity Editor tests and verify landscape locking through paywall presentation and dismissal on an iOS device.

Findings

🟠 Warning · F1 · UpdateSuperwallKitRequirement rewrites customized constraint lists

correctness · Editor/SuperwallPostBuildProcessor.cs:42

A developer who appends '< 4.19.0' to the existing '>= 4.12.10', '< 5.0' requirement gets '>= 4.19.1', '< 5.0', '< 4.19.0' on the next Append build. The substring replacement changes a hand-customized requirement into contradictory bounds, breaking dependency resolution instead of preserving the customization.

Match the complete version-constraint list before replacing it, allowing trailing CocoaPods options or comments but leaving additional version constraints untouched. Add a regression test for an appended upper bound.

🤖 Prompt to fix this finding with an AI agent

Findings from an automated review of commit 13120e4f295ef3043f9d4cd9d233e7efc3cb38d3. Verify each one against the current code before changing anything, fix only those that still apply, and keep each fix to the lines it names.

---

F1 · Warning · correctness · Editor/SuperwallPostBuildProcessor.cs:42
`UpdateSuperwallKitRequirement` rewrites customized constraint lists
A developer who appends `'< 4.19.0'` to the existing `'>= 4.12.10', '< 5.0'` requirement gets `'>= 4.19.1', '< 5.0', '< 4.19.0'` on the next Append build. The substring replacement changes a hand-customized requirement into contradictory bounds, breaking dependency resolution instead of preserving the customization.
Suggested fix: Match the complete version-constraint list before replacing it, allowing trailing CocoaPods options or comments but leaving additional version constraints untouched. Add a regression test for an appended upper bound.

_{13120e4 · What was checked, coverage and telemetry details are on the Maple / review check. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.}

[maple-review-bot]

Merged with 2 steps from "Before merge" still open. If they are done, tick them on the review comment; if not, now is the time.

• Manual · Confirm SuperwallKit 4.19.1 is published with Superwall-iOS #568 before merging.
• Manual · Run the Unity Editor tests and verify landscape locking through paywall presentation and dismissal on an iOS device.

[maple-review-bot]

1 inline note from Maple's review. The score and summary are in the review comment above.

[maple-review-bot]

Warning

UpdateSuperwallKitRequirement rewrites customized constraint lists

_{F1 · Warning · correctness}

A developer who appends '< 4.19.0' to the existing '>= 4.12.10', '< 5.0' requirement gets '>= 4.19.1', '< 5.0', '< 4.19.0' on the next Append build. The substring replacement changes a hand-customized requirement into contradictory bounds, breaking dependency resolution instead of preserving the customization.

Match the complete version-constraint list before replacing it, allowing trailing CocoaPods options or comments but leaving additional version constraints untouched. Add a regression test for an appended upper bound.

🤖 Prompt to fix with an AI agent

In `Editor/SuperwallPostBuildProcessor.cs:42`: `UpdateSuperwallKitRequirement` rewrites customized constraint lists.

A developer who appends `'< 4.19.0'` to the existing `'>= 4.12.10', '< 5.0'` requirement gets `'>= 4.19.1', '< 5.0', '< 4.19.0'` on the next Append build. The substring replacement changes a hand-customized requirement into contradictory bounds, breaking dependency resolution instead of preserving the customization.

Suggested fix: Match the complete version-constraint list before replacing it, allowing trailing CocoaPods options or comments but leaving additional version constraints untouched. Add a regression test for an appended upper bound.

Verify the problem exists at that location before changing it, and keep the fix to those lines.