drukscode/drukscode-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
drukscode-v2/docs/guide/app-actions/edit-common-config/activation.md
OpenCode AI e9899d2e6d
Some checks failed
Android CI Build / check (push) Has been cancelled
Details
Android CI Build / package-apks (push) Has been cancelled
Details
Docs Deploy / build (push) Has been cancelled
Details
Module Market Check / Validate modules/ (push) Has been cancelled
Details
Module Market Publish / Generate submissions.json (push) Has been cancelled
Details
Docs Deploy / deploy (push) Has been cancelled
Details
Initial DruksCode V2: fresh fork of web-to-app (f3b488e) with DruksCode identity 
- Package rename com.webtoapp -> br.com.drukstech.codeapp
- Product rename WebToApp/web-to-app -> DruksCode/drukscode
- Design system Wta* -> Dkc*
- applicationId br.com.drukstech.codeapp (.play for gplay flavor)
- rootProject.name DruksCode
- Fresh git history (upstream kept as remote for sync)
2026-09-12 02:42:02 +02:00

2.1 KiB
Raw Permalink Blame History

Activation Code Verification

Gate the generated app behind activation codes, so it runs only after a valid code is entered.

Where: the Activation code card in the Edit Common Config editor.

Options

  • Enable — turn activation gating on (activationEnabled).
  • Activation codes — the list of valid codes (activationCodeList).
  • Require every time — ask for the code on every launch, not just the first (activationRequireEveryTime).
  • Dialog config — customize the activation dialog (title, subtitle, input label, button text).
  • Remote activation — verify against your own HTTPS endpoint signed with EC P-256, with an offline policy (activationRemoteConfig).
  • Device binding (one-time codes) — remote-verification only (activationRemoteConfig.deviceBound). The verification request carries a device identifier and the server enforces per-code seats: each code is limited to 1 device by default (first device to activate claims the seat), so a code behaves as a one-time / single-device code. Other devices are rejected with the server's message. The claimed seat survives uninstall + reinstall on the same device. Requires a verification server that enforces binding — the reference worker does this out of the box via maxDevices.

Notes

  • Local verification checks codes on-device; remote verification calls your server. See the remote activation reference.
  • Device binding is impossible with local verification: the app has no shared state between devices, so any "one-time" claim on a purely local code cannot be enforced. Use remote verification with Device binding enabled for one-time codes.
  • The usage limit on a local usage-limited code counts app launches on the device after activation — it is not a per-code redemption limit and resets if app data is cleared.
  • The app list shows an activation chip on gated apps.