bug: Using the latest cli shows Not Authro

[onurio]

Version

3.4.1

Current behavior

Capawesome CLI Authorization Error Bug Report

Summary

apps:bundles:create command fails with "Not authorized" error despite successful authentication via both browser-based and token-based methods.

Environment

• CLI Version: 3.4.0 (also tested with 3.3.0 and 3.4.1 - same error)
• Platform: macOS (Darwin 24.6.0)
• Authentication Method: Browser-based and token-based (both tested)

Steps to Reproduce

1. Logged in using browser-based authentication: npx @capawesome/cli login
2. Also tested with token-based authentication
3. Verified login status: npx @capawesome/cli whoami (shows logged in successfully)
4. Built app for development: yarn build:dev
5. Attempted to create bundle:

npx @capawesome/cli apps:bundles:create \
  --app-id <APP_ID> \
  --path dist \
  --channel development \
  --private-key .capawesome_key.pem

Expected Behavior

Bundle should be created successfully and uploaded to the development channel.

Actual Behavior

Command fails with authorization error:

ERROR  Not authorized. Make sure to use the latest CLI version.

◐ Creating bundle...
If you think this is a bug, please open an issue at:
  https://github.com/capawesome-team/cli/issues/new/choose

Additional Testing

• Tested with CLI versions: 3.3.0, 3.4.0, 3.4.1 - all fail with same error
• whoami command successfully shows authenticated user
• Both browser-based and token-based authentication methods tested
• Private key file exists and is readable at .capawesome_key.pem
• dist directory exists and contains built app files
• Authentication appears successful (whoami works) but bundle creation fails

Additional Context

• Recently migrated from Capgo to Capawesome Live Update system
• App ID and private key are correct (used during app creation)
• No network connectivity issues observed
• User has appropriate permissions (owner/admin of the app)

Expected behavior

Expected Behavior

Bundle should be created successfully and uploaded to the development channel, similar to how the authentication flow works - after running whoami and confirming successful login, the apps:bundles:create command should proceed to upload the bundle without authorization errors.

Steps to reproduce

Steps to Reproduce

1. Logged in using browser-based authentication: npx @capawesome/cli login
2. Also tested with token-based authentication
3. Verified login status: npx @capawesome/cli whoami (shows logged in successfully)
4. Built app for development: yarn build:dev
5. Attempted to create bundle:

npx @capawesome/cli apps:bundles:create \
  --app-id <APP_ID> \
  --path dist \
  --channel development \
  --private-key .capawesome_key.pem

6. Command fails with "Not authorized" error despite successful authentication

Other information

No response

Doctor

npx capawesome doctor

╭────────────────────────────╮
│ │
│ NodeJS version: 20.11.0 │
│ NPM version: 11.6.2 │
│ CLI version: 3.4.1 │
│ OS: macOS 15.6 (Sequoia) │
│ │
╰────────────────────────────╯

Before submitting

• I have read and followed the bug report guidelines.
• I have attached links to possibly related issues and discussions.
• I understand that incomplete issues (e.g. without reproduction) are closed.

[robingenz]

Hi, thank you for reporting this. This error (Not authorized. Make sure to use the latest CLI version.) is only thrown if you try to access the app of an organization you are not a member of. What's the app ID, organization ID (see here) and user ID (see here)?

[onurio]

@robingenz thank you this indeed was a wrong app id. sorry about that.