Skip to content

docs(native-dart, native-kotlin, native-swift): correct setup steps; add constructor, option and error tables - #1642

Draft
xyos wants to merge 6 commits into
aws:mainfrom
xyos:docs/readme-native-sdks
Draft

xyos wants to merge 6 commits into
aws:mainfrom
xyos:docs/readme-native-sdks

Conversation

@xyos

@xyos xyos commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Problem

The READMEs of the Dart, Kotlin and Swift SDKs had setup steps that do not work and long paragraphs that hold many rules each (48 prose lines over 400 characters in 13 files, 17 of them in native/swift/README.md).

  • native/dart/README.md set a spec: option in build.yaml that the builder does not read, and required Dart 3.3+ where the packages require 3.11.
  • The 155-line "Using Auth" section has the same text in native/dart/README.md and in native/dart/packages/blocks_runtime/README.md.
  • The Kotlin example apps said to run the npm scripts from example/typescript/aws-blocks, whose package.json has none.
  • No Dart README listed the parameters of Blocks or BlocksClient, or the return types and exceptions of the OidcClient members; the Kotlin README had no list of the exceptions a call throws.

Issue #, if available:

Changes

Dart (native/dart)

  • README.md: the builder applies itself (packages/blocks_codegen/build.yaml:5-6) and reads only fail_on_collision and native_package_opt_out (packages/blocks_codegen/lib/builder.dart:9-15). Requirements are Dart 3.11+ (pubspec.yaml:9 of both packages) and Flutter 3.41+ for blocks_runtime_flutter only. example/ is described as end-to-end tests, not a demo Flutter app.
  • README.md: "Using Auth" is the heading, six rules (two of them fail without an error when skipped; one says what each platform passes to signIn; one says a sign-in that ends without a redirect throws OidcCancelledException) and a link to the same section of the blocks_runtime README.
  • README.md: new "Configuration" with the generated Blocks constructor (packages/blocks_codegen/lib/src/generator.dart:875,881). On an Android emulator it says to forward the port with adb reverse first: rewriteLocalhost gives the identity provider a redirect URI on 10.0.2.2, because the client builds it from the base URL (packages/blocks_runtime/lib/src/oidc_client.dart:223-235,517).
  • README.md: "Errors" is a section of its own. It holds the BlocksException table main has (packages/blocks_runtime/lib/src/blocks_exception.dart:16-111), the rules for matching an error by name as a list, and the HTTP status and 401 retry rules as a list (packages/blocks_runtime/lib/src/blocks_client.dart:84-89,181-209). Two items are new: a 401 without an authProvider is not retried, and a result that is missing for a method whose result is not nullable throws a TypeError, or a TransferableException for an unbound or declared native transferable (native/codegen-fixtures/17-transferables/dart/client.dart:59, 27-declared-transferable-bindings/dart/client.dart:100, packages/blocks_runtime/lib/src/transferable_descriptor.dart:11-15). "How it works", "What you get", "Project structure" and "How the codegen works" are removed; the typed OIDC sample is in the blocks_runtime README, which is linked.
  • packages/blocks_runtime/README.md: "Using Auth" keeps the sample and rules it has on main, "Federated sign-in on each platform" included; its two opening paragraphs are lists, and the signOut() rule lists its four outcomes as sub-items. New BlocksClient constructor table (lib/src/blocks_client.dart:32-40,109-121) and a sample that passes a BlocksClient to a generated API class, because the generated Blocks takes none (packages/blocks_codegen/lib/src/generator.dart:875-892). New "OidcClient" section: a member table with return types (lib/src/oidc_client.dart:77,153,159,259,308,432,650,866,986) and an OidcException table of four rows (lib/src/oidc_exception.dart:13-44). restore(), signOut() and a token refresh throw ApiException and TransportException (lib/src/oidc_client.dart:797-808,887-894,1011-1055), which the list above the table says.
  • packages/blocks_codegen/README.md: table of CLI flags and build.yaml options (bin/blocks_codegen.dart:9-32); the arm-naming rules are a list.
  • packages/blocks_runtime_flutter/README.md: the paragraph on how FlutterBrowserLauncher ends a sign-in is a list of its three cases (lib/src/flutter_browser_launcher.dart:87-96,102-107,123-132), and one list item says a desktop app calls signIn without a launcher.
  • example/README.md: four Auth blocks, not three (test-apps/native-bindings/aws-blocks/index.ts:65,77,109,138); the suite list gains rest_tuple_params_test.dart (bin/e2e_test.dart:28); the OIDC suite is not local only (bin/e2e/oidc_test.dart:141) and also signs in through the loopback listener (bin/e2e/oidc_test.dart:341).

Fixtures (native/codegen-fixtures/README.md): "Workflow After Codegen Changes" is first and links to each check; the Swift and Kotlin compile checks are lists; the live Auth check is a table; the codegen-error.txt sentence is part of the dart/ list entry.

Kotlin (native/kotlin)

  • README.md: the Kotlin 2.2.10 badge is removed (gradle/libs.versions.toml:3 is 2.2.21). New "Errors" table: ApiException, TransportException and ClientClosedException from runtime/src/commonMain/kotlin/com/aws/blocks/kotlin/BlocksClient.kt:55,70-136 and the generated null-result guard (codegen/src/main/java/com/aws/blocks/kotlin/generator/KotlinCodeGenerator.kt:1964-1971); the four OidcException subclasses (runtime/src/commonMain/kotlin/com/aws/blocks/kotlin/oidc/OidcException.kt:5-17) and FileTransferException (runtime/src/commonMain/kotlin/com/aws/blocks/kotlin/exceptions/FileTransferException.kt:13). "Generated types" is split into "Open records", "Unions" and "Names". "Support by Target" is one sentence.
  • example/android/README.md, example/kmp/README.md: "Prerequisites" links to the backend README's "Running" section (the scripts are in example/typescript/package.json:12-37). Sign-in names the stub IdP and a Google OAuth client. KMP: App constructs Blocks with Blocks.defaultServer (composeApp/src/commonMain/kotlin/com/aws/blocks/example/App.kt:40).
  • example/typescript/README.md: the stub IdP comes before the Google setup; the upgrade note is one line under "Running". The sentence saying the published package cannot build the backend is kept as on main.

Swift (native/swift)

  • README.md: x-blocks-type-name is described by what the generator reads (Sources/BlocksCodegen/CodegenModelBuilder.swift:274-287), without a pull request number. Blocks(server:session:tokenStore:) is a table under "Configuration" (Sources/BlocksCodegen/SwiftCodeGenerator+EntryPoint.swift:85-96, Sources/BlocksRuntime/BlocksClient.swift:59-80), followed by "Lifetime", which says realtime channels and file transfers use sessions of their own (Sources/BlocksRuntime/BlocksRuntimeSession.swift:13-34). "Features" is "Generated types" in seven sections; "Transferables" holds main's item on how a realtime subscription ends, unchanged. The launcher options are a table, and the errors signIn throws are a table of the eight OIDCError cases and CancellationError (Sources/BlocksRuntime/OIDC/OIDCClient.swift:858-873). Comparisons with the other SDKs and statements about earlier releases are removed.
  • Demo/README.md: step 1 says the published @aws-blocks/blocks cannot build the backend until a release includes Auth, and lists the three steps that run it against a checkout of this repository. Step 4 keeps the CLI command, names the two files the demo target compiles, and has two list items: the Xcode command plugin run on the BlocksDemo project (Plugins/BlocksCodegenCommandPlugin/Plugin.swift:96-113) and the build plugin with what the demo target needs for it. swift package generate-code-from-blocks-spec is not listed for the demo: it covers the package's own targets (Plugin.swift:31). The Package.swift snippet is in the Swift README. A device needs BLOCKS_SPEC_STAGE=production npm run spec (packages/core/src/scripts/generate-spec.ts:1128-1130, packages/core/src/scripts/deploy.ts:385). The folder tree is two lines.
  • Demo/typescript-demo/README.md: says what the backend is for; "Commands" gains npm run spec.
File Lines Words Lines over 400 chars
native/codegen-fixtures/README.md 122 → 137 804 → 817 4 → 1
native/dart/README.md 328 → 170 2878 → 1466 10 → 1
native/dart/example/README.md 66 → 65 448 → 436 0 → 0
native/dart/packages/blocks_codegen/README.md 49 → 75 288 → 479 0 → 0
native/dart/packages/blocks_runtime/README.md 196 → 286 1944 → 3064 8 → 5
native/dart/packages/blocks_runtime_flutter/README.md 56 → 62 257 → 286 1 → 0
native/kotlin/README.md 187 → 227 1591 → 1789 3 → 0
native/kotlin/example/android/README.md 66 → 55 450 → 318 0 → 0
native/kotlin/example/kmp/README.md 76 → 67 529 → 433 0 → 0
native/kotlin/example/typescript/README.md 171 → 177 1574 → 1483 4 → 1
native/swift/Demo/README.md 132 → 97 583 → 577 1 → 0
native/swift/Demo/typescript-demo/README.md 37 → 22 239 → 175 0 → 0
native/swift/README.md 215 → 296 3272 → 3300 17 → 3
Total 1739 → 1774 15133 → 14899 48 → 11

Changesets: one for aws-blocks-kotlin and one for aws-blocks-swift, each patch. The Dart SDK has no changeset directory, and no package under packages/ changes, so there is no other changeset.

Look hardest at:

  • "Using Auth" in the Dart READMEs. fix(native-dart): restore, sign-out and session fixes for the OIDC client from getClient() #1479 added the same section, word for word, to native/dart/README.md and to native/dart/packages/blocks_runtime/README.md; feat(native-dart): sign in on desktop through a loopback listener #1499, feat(native-dart)!: let a sign-in browser launch be cancelled #1571 and feat(native-dart)!: one shared error taxonomy for the Dart client #1574 then edited both copies the same way. This change keeps it once, in the runtime README, and leaves in the SDK README the heading, six rules and a link to it. That reverses part of four merged changes, so a maintainer should confirm it; restoring the second copy is a one-file change.
  • The new Dart tables (Blocks, BlocksClient, OidcClient, OidcException, codegen options): every cell is new text derived from the source. The member table leaves out refresh(), getAccessToken() and onAuthFailure(). The BlocksException table in "Errors" is main's, unchanged.
  • "Errors" in native/dart/README.md keeps main's sentence "Every error the runtime throws is a BlocksException" and lists beside it the cases where that does not hold: a TypeError from the generated cast for a missing result (native/codegen-fixtures/41-void-methods/dart/client.dart:32), and the StateError, ArgumentError, FormatException and TypeError an OidcClient throws (packages/blocks_runtime/lib/src/oidc_client.dart:358,445,468,599-601,719,726,736, packages/blocks_runtime/lib/src/loopback_session_io.dart:108-113).
  • The Dart builder step: no spec: option, every *.spec.json becomes *.blocks.dart.
  • native/swift/Demo/README.md going from 132 to 97 lines: the Xcode steps for both plugins are derived from the plugin sources and the project file, and were not run in Xcode.
  • The checkout steps in step 1 of native/swift/Demo/README.md were run on main ea7108832: without npm install and with the link, npm run dev served the API on port 3001 and npm run spec wrote a spec with the local server. On that first start Vite, which serves the web frontend, logged a dependency-scan error for the aws-blocks package, which the dev server generates the client for while starting.
  • The Kotlin example READMEs now depend on the backend README for the shared setup.

Not changed on purpose: the sample and the rules of "Using Auth" as they are on main, and the two Flutter samples; build_runner: ^2.4.0 and "Node.js 22+" in the Dart README; the version in the Swift quick start; "Xcode 26+"; the Kotlin "Requirements" list; the .changeset/README.md and fixture-stubs/README.md files.

Open questions:

  • On main no source writes x-blocks-type-name into a spec; only the Swift generator reads it. fix(native-dart)!: one shared AuthActionInput for every Auth block #1599 makes core write it, and with the hint the generator marks AuthApi.SetAuthState.Input deprecated. Whichever of the two merges second switches the "Using Auth" sample to AuthActionInput?.
  • OidcClient.signInDirect reports a state mismatch as a StateError (oidc_client.dart:358). A 2xx answer of the authorize-params route that is not the expected JSON is a FormatException or a TypeError (oidc_client.dart:599-601), although the doc comment of signIn says it is a TransportException (:430-431). A 2xx exchange answer whose user or tokens have the wrong type is a TypeError (:719,726,736). The README documents what the code does. The review's answer: the Kotlin client wraps these in its OidcException subclasses with a cause, and Dart doing the same is a runtime change; OidcCallbackException takes no cause yet (oidc_exception.dart:36-38).
  • main says every error the Dart runtime throws is a BlocksException, while signIn and signInDirect still throw StateError (oidc_client.dart:358,445,468), a signIn without a launcher throws ArgumentError for an authorize URL that is neither https nor http on a loopback host (loopback_session_io.dart:108-113), and BlocksClient.call throws ArgumentError (blocks_client.dart:74-80). The READMEs keep the sentence and list the exceptions.
  • "Using Auth" advises a verified App Link or Universal Link as relayTo; the doc comment of signIn requires a custom-scheme URI (oidc_client.dart:407-408). Not changed.
  • The Dart README has no supported-platforms table like the Kotlin and Swift READMEs; the Dart sources do not state the tested platforms.
  • Kotlin 2.1+, Gradle 7.4+ and Android Gradle Plugin 7.1+ are not checked against the build files; the packages' own build_runner floor is ^2.16.2.

Answered in review, no change:

  • native/swift/README.md pins .upToNextMinor(from: "0.2.0") while the newest tag of the Swift package is 0.1.1. 0.2.0 is the next release (31 pending minor changesets under native/swift/.changeset), and the README documents what that release contains.
  • native/swift/Demo/README.md requires Xcode 26+ while swift-demo/project.yml says xcodeVersion: "15.0". The README is right: native/swift/Package.swift declares swift-tools-version: 6.2. The value in project.yml is for a separate change.

Changed after review:

  • Kotlin backend README: the sentence about the published package is back, as on main. The Swift demo README gains the same statement for its backend, which imports Auth the same way.
  • Kotlin README: the errors table gains the OidcException subclasses and FileTransferException.
  • Dart README, "Errors": a result that is missing for a method whose result is not nullable throws a TypeError, or a TransferableException when the result is an unbound or declared native transferable. The other items the first review round asked for (no HTTP status check, a null result for a gateway's own error body) are gone, because main now checks the status and throws a TransportException.
  • blocks_runtime and blocks_runtime_flutter READMEs: the statements that a sign-in the user backs out of does not complete are gone, because on main FlutterBrowserLauncher throws OidcCancelledException in that case and cancel: works with a launcher.
  • Swift README: the errors table lists every OIDCError case.
  • Swift demo README: the command-line form of the command plugin is no longer listed for the demo. The Xcode form stays: the plugin has an XcodeCommandPlugin extension (Plugins/BlocksCodegenCommandPlugin/Plugin.swift:96-113) that reads swift-demo/blocks.spec.json and writes swift-demo/Generated/, the two files the project compiles. The build plugin item says what the demo target needs.
  • Dart README: adb reverse first on an Android emulator.
  • blocks_runtime README: the generated Blocks takes no client.
  • Kotlin example READMEs: "a small change in the backend's aws-blocks/index.ts".
  • Swift README, "Using Auth" sample: unchanged, see the first open question.

Carried from main: six changes merged after this pull request was opened are applied to the revised text.

Related pull requests: this supersedes none. Open pull requests that touch the same files:

Whichever merges second rebases.

Part of a set of README revisions: #1635 (core), #1636 (hosting and pipeline), #1637 (bb-agent and bb-knowledge-base), #1638 (bb-auth and auth-common), #1639 (the storage blocks), #1640 (compute, jobs, realtime, email and observability), #1641 (the guide, the scaffolder and its templates), #1643 (contributor docs). Each merges on its own.

Validation

Run on this branch alone at 9509fcc60, on main 8940cfd2f, with Node 22. All pass:

  • npm run build
  • the shipped-docs tests in packages/blocks (readme-links, docs-pointers, doc-snippets, imports-reference)
  • packages/blocks sandbox-dir-coverage (no tracked file names the old directory .blocks-sandbox)
  • packages/core readme-policies (the IAM policy JSON)
  • packages/bb-auth readme-recipes, first-admin, multi-block-snippets, users-cli, gate-diagnostics
  • packages/auth-common ui.react-types
  • packages/bb-kv-store readme.generated (every README snippet compiled) and legacy/runtime
  • packages/create-blocks-app npm test
  • npm run sync-docs:check
  • npm run check:imports
  • changeset-guard.ts validate-structure
  • changeset-guard.ts verify-coverage
  • changeset-guard.ts verify-umbrella
  • changeset-guard.ts block-major
  • every relative link and #anchor in the changed files, and every link into them from another Markdown file, resolves (checked with a script)

Run once on all the README branches of this set combined, as they were on an earlier main commit (e1e484465), and not run again after the rebases: packages/core unit suite, packages/blocks unit suite, packages/bb-kv-store unit suite, packages/bb-auth unit suite, packages/auth-common unit suite, npm run lint, npm run lint:deps and npm run check:api. All passed.

Not run locally: the full npm test across all workspaces, npm run test:e2e:local and the sandbox e2e suites. CI runs them.

No test was added: the tests listed above already read these READMEs, and the remaining statements are checked against the source by review.

Checklist

  • PR description included
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@changeset-bot

changeset-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ec9ca11

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

harsh62
harsh62 previously approved these changes Nov 18, 2026
Comment thread native/kotlin/README.md Resolved
Comment thread native/dart/README.md Resolved
Comment thread native/swift/README.md Resolved
Comment thread native/swift/Demo/README.md Resolved
Comment thread native/dart/README.md Resolved
Comment thread native/swift/README.md Resolved
Comment thread native/kotlin/example/android/README.md Resolved
Comment thread native/swift/README.md Resolved
Comment thread native/swift/Demo/README.md Resolved
xyos added 6 commits November 19, 2026 14:23
… constructor and error tables

The SDK README's `build.yaml` step showed a `spec:` option the builder does not read; it now says the builder applies itself, turns every `*.spec.json` into `*.blocks.dart`, and reads only `fail_on_collision` and `native_package_opt_out`.
"Requirements" said Dart 3.3+ and Flutter "for the demo app"; the packages require Dart 3.11, only `blocks_runtime_flutter` needs Flutter (3.41+), and `example/` holds end-to-end tests, not a demo Flutter app.
The "Using Auth" section had the same text in the SDK README and in the `blocks_runtime` README; it is kept in the `blocks_runtime` README, and the SDK README keeps the heading, six rules (one says what each platform passes to `signIn`, one that a sign-in ending without a redirect throws `OidcCancelledException`) and a link to it.
The SDK README documents the generated `Blocks` constructor under "Configuration". "Errors" keeps the `BlocksException` table and states the name-matching, HTTP status and 401-retry rules as lists; it adds that a 401 without an `authProvider` is not retried, what a missing result throws for a method whose result is not nullable, and which errors an `OidcClient` throws outside the taxonomy.
The `blocks_runtime` README documents the `BlocksClient` constructor, how to pass a `BlocksClient` to a generated API class (the generated `Blocks` takes none), the `OidcClient` members with their return types, and what each call throws: the four `OidcException` subclasses, `ApiException` and `TransportException` for `restore()`, `signOut()` and a token refresh, and the `StateError`, `ArgumentError`, `FormatException` and `TypeError` cases. The `blocks_codegen` README has a table of CLI flags and `build.yaml` options.
For an Android emulator the SDK README said to rewrite `localhost` to `10.0.2.2`; it now says to forward the port with `adb reverse` first, because the identity provider's redirect URI is built from the base URL.
The `blocks_runtime_flutter` README lists the three ways `FlutterBrowserLauncher` ends a sign-in with `OidcCancelledException` and says a desktop app calls `signIn` without a launcher.
The example README says the backend has four `Auth` blocks, not three, lists `rest_tuple_params_test.dart`, no longer calls the OIDC suite local only, and says the suite also signs in through the loopback listener.
"How it works", "What you get", "Project structure" and "How the codegen works" are removed from the SDK README; the typed OIDC provider details are in the `blocks_runtime` and `blocks_codegen` READMEs, which the SDK README links.
…EADME

"Workflow After Codegen Changes" was the last section and repeated the command of each check; it is now the first section and links to the section that holds each command.
The Swift and Kotlin compile checks were single paragraphs of more than 400 characters; each is now a list of what the check compiles, what it skips or treats as advisory, what it needs and which CI job runs it.
The live `Auth` fixture check is a table of fixture, what it mirrors and what is compared, for fixtures 18, 23 and 37.
The sentence saying `dart/` can hold `codegen-error.txt` is now part of the `dart/` entry in the structure list.
…ckend README for setup

The Android and KMP example READMEs said to run `npm install`, `npm run dev` and `npm run spec` from `example/typescript/aws-blocks`, whose `package.json` has no such scripts; both now link to the backend README's "Running" section.
Both also said there is no fake-user fallback for sign-in; they now name the two ways to sign in that the backend README documents, the stub IdP and a Google OAuth client.
The KMP README said `App` constructs `Blocks()`; it constructs `Blocks` with `Blocks.defaultServer`, and the README says so.
The SDK README drops a badge that said Kotlin 2.2.10 (the build uses 2.2.21), gains an "Errors" section for `ApiException`, `TransportException`, `ClientClosedException`, the four `OidcException` subclasses and `FileTransferException`, and splits "Generated types" into "Open records", "Unions" and "Names" with one rule per list item or table row.
The backend README presents the stub IdP before the Google setup and states the `userId`-keyed table upgrade as one present-tense line under "Running".
…en the demo README

The SDK README said the backend writes the `x-blocks-type-name` hint for a TypeScript type alias and referred to a pull request number and "an older backend"; it now states what the generator produces with and without the hint, and lists a name that isn't a Swift identifier as a third reason for a nested `Input` with a warning.
The demo README told a reader with a physical device to deploy and "regenerate" without a command; it now names `BLOCKS_SPEC_STAGE=production npm run spec`, because plain `npm run spec` reads the dev server's configuration.
`Blocks(server:session:tokenStore:)` is documented under "Configuration" as a table of parameters and defaults, followed by "Lifetime"; "Features" is now "Generated types" with one rule per list item; the launcher options are a table, and the errors `signIn` throws are a table of the eight `OIDCError` cases and `CancellationError`.
The demo README replaces the four "Option" sections for code generation with the CLI command the demo uses, the two generated files the demo target compiles, and two list items: the Xcode command plugin run on the `BlocksDemo` project, and the build plugin with what the demo target needs for it. `swift package generate-code-from-blocks-spec` is no longer listed for the demo: from `native/swift/` it generates into the package's own test targets. An out-of-date per-file tree becomes two lines.
The demo README's step 1 says the published `@aws-blocks/blocks` cannot build the backend until a release includes `Auth`, and how to run the backend against the checkout.
The demo backend README says it is the backend of the Swift demo, lists `npm run spec` under "Commands" and states the docs pointer once.
The "Lifetime" list says realtime channels and file transfers use sessions of their own, shared by every instance: realtime sockets have a `URLSession` separate from the one for file transfers.

# Conflicts:
#	native/swift/Demo/README.md
#	native/swift/README.md
…en the demo README

The SDK README said the backend writes the `x-blocks-type-name` hint for a TypeScript type alias and referred to a pull request number and "an older backend"; it now states what the generator produces with and without the hint, and lists a name that isn't a Swift identifier as a third reason for a nested `Input` with a warning.
The demo README told a reader with a physical device to deploy and "regenerate" without a command; it now names `BLOCKS_SPEC_STAGE=production npm run spec`, because plain `npm run spec` reads the dev server's configuration.
`Blocks(server:session:tokenStore:)` is documented under "Configuration" as a table of parameters and defaults, followed by "Lifetime"; "Features" is now "Generated types" with one rule per list item; the launcher options are a table, and the errors `signIn` throws are a table of the eight `OIDCError` cases and `CancellationError`.
The demo README replaces the four "Option" sections for code generation with the CLI command the demo uses, the two generated files the demo target compiles, and two list items: the Xcode command plugin run on the `BlocksDemo` project, and the build plugin with what the demo target needs for it. `swift package generate-code-from-blocks-spec` is no longer listed for the demo: from `native/swift/` it generates into the package's own test targets. An out-of-date per-file tree becomes two lines.
The demo README's step 1 says the published `@aws-blocks/blocks` cannot build the backend until a release includes `Auth`, and how to run the backend against the checkout.
The demo backend README says it is the backend of the Swift demo, lists `npm run spec` under "Commands" and states the docs pointer once.
The "Lifetime" list says realtime channels and file transfers use sessions of their own, shared by every instance: realtime sockets have a `URLSession` separate from the one for file transfers.
@xyos
xyos force-pushed the docs/readme-native-sdks branch from 9509fcc to c8a5818 Compare November 19, 2026 14:25

This branch has not been deployed

No deployments
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.

3 participants