Skip to content

Release 9.7.0#321

Merged
SpertsyanKM merged 9 commits into
mainfrom
release/9.7.0
Jul 17, 2026
Merged

Release 9.7.0#321
SpertsyanKM merged 9 commits into
mainfrom
release/9.7.0

Conversation

@SpertsyanKM

Copy link
Copy Markdown
Contributor

Release PR

What's New

  • No-Codes: new LoadScreen(contextKey, onSuccess, onError) method — loads a screen without presenting it and returns a typed NoCodesScreen with id, context key, default selected product id and typed DefaultVariables
  • No-Codes: new optional NoCodesCustomActionDelegate interface — implement it alongside your NoCodesDelegate to receive custom actions configured in the builder
  • No-Codes: support for custom purchase loaders — if one is set in the builder, the SDK won't show the native spinner
  • No-Codes: fixed original error details being lost when wrapping client errors
  • Updated native SDKs: iOS Qonversion 6.13.0, Android No-Codes 1.10.0

suriksarkisyan and others added 9 commits May 5, 2026 14:21
Rollout of the release automation piloted in sandwich-sdk: release.yml
(workflow_dispatch) runs the whole release via the shared workflow —
version calculation, release PRs, bot approval, CI gate, merge — and
publish_release.yml creates the GitHub release when the release PR
merges to main, so the publish workflow fires on release:[released]
as before.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GjdKcoaoecn6TKWmnUZzji
…DEV-1181)

Deleted: manual prerelease dispatch lanes (replaced by the Release
workflow), tag-triggered release PR creation (prerelease/* tags no longer
drive releases) and the Development Build prerelease on pushes to main
(the GitHub release is now created directly by publish_release).
Publish, checks, stale and upgrade_sandwich workflows are untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GjdKcoaoecn6TKWmnUZzji
…omation-rollout-to-all-sdk-repos

Add one-click release workflows (DEV-1181)
…(DEV-1192)

Bump sandwich to 7.10.1. LoadScreen(contextKey, onSuccess, onError)
returns a typed NoCodesScreen (id, contextKey, defaultSelectedProductId,
typed defaultVariables); requests are correlated by contextKey carried
in both success and failure payloads. Custom builder actions surface
via the new optional NoCodesCustomActionDelegate interface (kept
separate from NoCodesDelegate for source compatibility on Unity 2018.3,
which has no default interface methods).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KQEJXqfVNxqoUcKXhSPhWn
…code (DEV-1192)

An unparseable success payload now fails the correlated callbacks
instead of leaving them pending forever, and unsupported platforms
(noop wrapper) fail synchronously instead of never responding. Map the
ClientError code both natives emit since sandwich 7.10.1.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KQEJXqfVNxqoUcKXhSPhWn
The pending-callback fix only covered the null-return path; an anomalous
payload throwing inside the NoCodesScreen constructor still escaped into
the UnitySendMessage handler and leaked the correlated callbacks. Return
null on mapping failure so the existing parse-error path fails them.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BVh5VVyvxemyHT2oRSyXWK
…loadscreen-defaultvariables-and-custom-action

Bridge No-Codes loadScreen, defaultVariables and custom action event (DEV-1192)
@SpertsyanKM SpertsyanKM added autocreated one-click-release Pull requests handled by the one-click release automation labels Jul 17, 2026
@SpertsyanKM
SpertsyanKM merged commit 19b8f21 into main Jul 17, 2026
@SpertsyanKM
SpertsyanKM deleted the release/9.7.0 branch July 17, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autocreated one-click-release Pull requests handled by the one-click release automation

Development

Successfully merging this pull request may close these issues.

3 participants