SDK Versions

You choose the Flutter, Android, and iOS versions your project builds with. Change them from the workspace, ask the agent in chat, or let the agent raise a version when a feature needs it.

Where to find it

Open Workspace → Build → SDK Versions. The screen lists the versions currently in use.

What you can change

Versions are grouped by platform:

• Flutter — Flutter SDK
• Android — Compile SDK, Min SDK, Target SDK, NDK, Gradle, Android Gradle Plugin (AGP), Kotlin, and Java
• iOS — Xcode and Deployment Target

Each dropdown lists released versions from the official catalogs, so you pick a version that exists. Android SDK fields are API levels, such as API 36. Java versions mark long-term support releases. Longer lists, such as Android Gradle Plugin (AGP), Kotlin, and NDK, load more versions as you scroll.

Compatibility

Not every combination of these versions can build together. The Flutter SDK is fixed for the migration. The agent keeps that Flutter version and checks every other version against it.

The agent applies the Android and iOS versions you asked for when they work with that Flutter SDK. When a requested version cannot be used, it picks a compatible one instead. There is no guarantee that every version you name will be the one that ends up in the project.

Changing versions from the UI

1. Open SDK Versions

   Go to Workspace → Build → SDK Versions.

2. Pick the versions you want

   Open a dropdown and select a version. Changed fields show a Changed label. Cancel discards the draft and restores the current versions.

3. Review the confirmation

   Click Update versions. A dialog lists every change, from the current version to the one you chose, and explains that the agent will migrate the project.

4. Start the migration

   Click Start migration. Primio confirms with Migration started — follow along in chat, returns you to the preview, and posts an SDK version update requested card in the conversation while the agent rewrites the project.

Start migration stays disabled while the agent is already working. Wait for the current task to finish, then try again.

Asking the agent directly

You can skip the screen and describe the change in chat. The agent reads the versions your project uses and applies a compatible update. For example:

• “Upgrade Flutter to the latest stable release.”
• “Raise the Android target SDK to 36 and bump the Android Gradle Plugin (AGP) so the project still builds.”

The same SDK version update requested card appears in chat, and the migration runs as agent work.

When the agent updates versions for you

While building a feature, the agent may need a newer plugin or a platform API your current versions do not support. It can raise the relevant versions as part of that work. The change shows up in the conversation, the same way a change you requested does.

Confirming the migration

The agent can currently only verify the Dart part of the migration. A finished chat does not show whether the Android or iOS toolchain still builds.

The first web preview, web publish, PWA export, Android build, or iOS build after a version change can take longer while Primio provisions the SDK the project now uses.

After the migration, start a native build for each platform you changed: an APK or AAB from Workspace → Publish → Android, or an IPA from Workspace → Publish → iOS. A successful native build is the confirmation that the version change completed. See Android Builds and iOS Builds.

If a native build fails, open the failed build and click Try to fix. That sends the build error to the agent so it can repair the native project.

Cost and reverting

Caution

A version change is agent work. It rewrites your project’s build files and source to migrate the toolchain, it consumes tokens, and it can take a while. The request is a checkpoint: use Revert this on the chat card to roll the project back. See Rollback.

If something goes wrong

• Agent is currently working. Wait for the current task to finish. The confirmation button reads Agent is working until then.
• Not enough tokens. The migration does not start. Upgrade plan or wait for your balance to reset, then try again. See Token System.
• A native build fails after the migration. Click Try to fix on the failed build. If that does not recover the project, roll back the checkpoint and retry a smaller step, such as one platform at a time. See Debugging & Fixing Errors.

Next steps

• Build Modes — switch a platform between Release and Debug
• Android Builds — build APK and AAB files
• iOS Builds — build IPA files for TestFlight and the App Store
• Rollback — undo a migration that went the wrong way