Changes to the SDKs, the CLI, the API, the customer portal, the dashboard and the website. Filter by what you use, or follow it in a reader with the Atom feed.
Settings > Payments links a Paddle account with an API key, beside Stripe. Price pickers, archive offers, held sales and License detail work with Paddle, and the docs have a new page, Selling through Paddle. Paddle opens no checkout until its account has a default payment link, so the card warns while one is missing.
Link a Paddle account in Settings > Payments by pasting an API key, live or sandbox. A completed Paddle checkout issues the license key, refunds covering the whole payment or a chargeback take it back, a chargeback Paddle wins back returns it, and renewals and cancellations follow the subscription. The checkout lookup takes a Paddle transaction id, and the customer portal's Manage billing opens Paddle's portal.
The feature list, the plan list and the platforms answer now say how an App Store build restores a license: Key pickup, a code emailed to the address on the license, with no key to type.
The home page lists the Dart and Flutter SDK beside the others, with its install line and pub.dev link, and the docs have its page: setup, the calls, restoring a license in an App Store build, and how a phone is identified.
The new keygrant package licenses Flutter apps on iOS, iPadOS, Android, Windows, macOS and Linux, with the same offline leases, trials, license files, metered uses and key pickup as the other SDKs.
Turn on Key pickup for a product and your app can restore a customer's license with a code sent to the email they bought with, no key to type, as App Store builds need. Call restoreByEmail(email, code) after pickUp(email).
Sign-up records which version of the terms you accepted, and when. If you joined another way, the dashboard asks you to accept them once.
keygrant.dev now has a terms of service and a privacy policy, linked from every page footer and from sign-up.
From CLI 0.5.2, the Windows keygrant file on the release page is signed with Authenticode.
From CLI 0.5.1, the macOS keygrant files on the release page are signed with a Developer ID and notarized by Apple.
keygrant licenses user-lock <key> <off|email|code> sets who can activate a new device on a key. licenses get and products now show who can activate.
keygrant licenses test --scenario used-up makes a test license whose first meter has no uses left, so you can see how your app handles it.
Each CLI release now attaches the keygrant command as one file for Linux, macOS and Windows on its GitHub release page. It reads your key from KEYGRANT_API_KEY.
keygrant licenses uses can now set whether a meter comes back each billing period (--resets) and take a meter off a key (--remove).
keygrant licenses issue --meter exports=1000 gives a new key meters of its own in place of its model's, and --no-meters gives it none.
keygrant licenses devices <key> lists the devices a license is active on, with the activation id that keygrant licenses free-device takes.
keygrant licenses get says whether a key is typed, sent as a key file or sent as a license file, and keygrant products says which models send files.
GET /v1/licenses/:key/activations lists the devices a license is active on, the most recently seen first, each with the activation id that DELETE /v1/licenses/:key/activations/:id frees.
What's New in the dashboard, and a changelog at keygrant.dev/changelog. Filter by SDK, API, dashboard or website, and follow it by feed.
The server API reference now documents listing your products and their license models, and making a test license in a chosen state, with their limits. See /docs/api/server.