Deployment error: Debug Failure. False expression when deploy extension
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- cli
Research direction
Start with the deployment flow in @rocket.chat/apps-cli/lib/commands/deploy.js, especially asyncSubmitData at line 100, and review the reported package.json. Reproduce the deploy command with the shown dependencies and inspect where the false assertion is triggered. Done means the extension deploys successfully or the CLI reports a useful actionable error.
Written by the indexing model from the issue text.
Description
Here is the package json of my extension
{
"devDependencies": {
"@rocket.chat/apps-engine": "^1.12.0",
"@types/node": "^10.12.14",
"tslint": "^5.10.0",
"typescript": "^3.7.3"
}
}
When i deploy app, i got the following problem. Pls help!
Error: Deployment error: Debug Failure. False expression.
at Deploy.asyncSubmitData (/usr/local/lib/node_modules/@rocket.chat/apps-cli/lib/commands/deploy.js:100:19)
at async Deploy.run (/usr/local/lib/node_modules/@rocket.chat/apps-cli/lib/commands/deploy.js:47:9)
at async Deploy._run (/usr/local/lib/node_modules/@rocket.chat/apps-cli/node_modules/@oclif/command/lib/command.js:44:20)
at async Config.runCommand (/usr/local/lib/node_modules/@rocket.chat/apps-cli/node_modules/@oclif/config/lib/config.js:172:9)
at async Main.run (/usr/local/lib/node_modules/@rocket.chat/apps-cli/node_modules/@oclif/command/lib/main.js:21:9)
at async Main._run (/usr/local/lib/node_modules/@rocket.chat/apps-cli/node_modules/@oclif/command/lib/command.js:44:20)
- Dominant language
- TypeScript
- Stars
- 49
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/Rocket.Chat.Apps-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
RocketChat/Rocket.Chat.Apps-cli#181 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
RocketChat/Rocket.Chat.Apps-cli#177 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
RocketChat/Rocket.Chat.Apps-cli#173 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
All issues in RocketChat/Rocket.Chat.Apps-cli
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·