Skip to content

SDK 0.3.1: typed applyCode errors and version header - #3

Merged
cursor[bot] merged 1 commit into
mainfrom
cursor/sdk-0-3-1-typed-redeem-errors-7c10
Oct 9, 2026
Merged

cursor[bot] merged 1 commit into
mainfrom
cursor/sdk-0-3-1-typed-redeem-errors-7c10

Conversation

@KennyYe

@KennyYe KennyYe commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

Fix release for redeem / applyCode error handling.

  • Check HTTP status on every SDK request; never treat non-2xx bodies as success
  • Typed TapAppLinkApplyCodeException cases: unknownCode, inactiveCode, wrongEnvironment, network/timeout, other(status, message)
  • Map from body error (unknown_code, inactive_code, wrong_environment) with status fallbacks (404 / 410)
  • Send X-TapAppLink-SDK-Version: 0.3.1 on all requests
  • Unit tests for legacy 404 + body and new 410/400 paths
  • CHANGELOG, version bump to 0.3.1, README UI-state mapping for each outcome

Test plan

  • dart format, flutter analyze, flutter test locally
  • CI green on this PR
  • After squash-merge: tag v0.3.1 and confirm pub.dev publish workflow
Open in Web Open in Cursor 

Check HTTP status on every request, map redeem failures to typed
TapAppLinkApplyCodeException cases, send X-TapAppLink-SDK-Version,
and document UI copy for each applyCode outcome.

Co-authored-by: Kenny Ye <KennyYe@users.noreply.github.com>
@KennyYe
KennyYe marked this pull request as ready for review October 9, 2026 17:14
@cursor
cursor Bot merged commit 1c0464d into main Oct 9, 2026
2 checks passed
@cursor
cursor Bot deleted the cursor/sdk-0-3-1-typed-redeem-errors-7c10 branch October 9, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants