Can you make the errors logs a bit clearer?
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- android, ios, react-native, typescript
- 领域
- documentation, mobile, testing
调研方向
首先,使用提供的 Owl 配置重现报告的 yarn owl test --platform ios 和 Android ./gradlew assembleDebug --console plain -PisOwlBuild=true 失败。跟踪这些命令如何报告错误,并检查 Android 设置文档;当日志更具可操作性,且文档中的 Android 设置反映所需流程时,即视为完成。
由索引模型根据 Issue 内容生成。
描述
Is there an existing issue for this?
- I have searched the existing issues
Code of Conduct
- I agree to follow this project's Code of Conduct
Question
Hi there. I am in the midst of investigating react native owl for my company and I am having a hard time getting set up. My first issue has to do with iOS. I can build the app using yarn owl build --platform. Fine. For some strange reason whenever i run yarn owl test --platform iOS the script is failing with
$ /Users/curtis/Documents/metamask-mobile/node_modules/.bin/owl test --platform ios
[OWL - CLI] Starting websocket server.
[OWL - CLI] Running tests on ios.
Error: Command failed with ENOENT: xcrun simctl status_bar iPhone-16-Pro override --time 9:41
spawn xcrun ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn xcrun',
path: 'xcrun',
spawnargs: [
'simctl',
'status_bar',
'iPhone-16-Pro',
'override',
'--time',
'9:41'
],
originalMessage: 'spawn xcrun ENOENT',
shortMessage: 'Command failed with ENOENT: xcrun simctl status_bar iPhone-16-Pro override --time 9:41\n' +
'spawn xcrun ENOENT',
command: 'xcrun simctl status_bar iPhone-16-Pro override --time 9:41',
escapedCommand: 'xcrun simctl status_bar iPhone-16-Pro override --time "9:41"',
exitCode: undefined,
signal: undefined,
signalDescription: undefined,
stdout: undefined,
stderr: undefined,
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
At first I thought this had to do with a previously reported issue but then if i were to run xcrun simctl status_bar iPhone-16-Pro override --time 9:41 as a stand alone command, the simulator time updates as expected. I am at the point where the script fails because it is unable to set the device time. Can these error logs be a bit more verbose?
Secondly, I cannot get Android to build.
BUILD FAILED in 29s
120 actionable tasks: 7 executed, 113 up-to-date
Error: Command failed with exit code 1: ./gradlew assembleDebug --console plain -PisOwlBuild=true
at makeError (/Users/curtis/Documents/metamask-mobile/node_modules/react-native-owl/node_modules/execa/lib/error.js:60:11)
at handlePromise (/Users/curtis/Documents/metamask-mobile/node_modules/react-native-owl/node_modules/execa/index.js:118:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
shortMessage: 'Command failed with exit code 1: ./gradlew assembleDebug --console plain -PisOwlBuild=true',
command: './gradlew assembleDebug --console plain -PisOwlBuild=true',
escapedCommand: '"./gradlew" assembleDebug --console plain "-PisOwlBuild=true"',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: undefined,
stderr: undefined,
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
Specify --help for available options
error Command failed with exit code 1.
Is it possible to update the documentation to reflect the android setup?
Here is my owl config by the way:
{
"ios": {
"workspace": "ios/MetaMask.xcworkspace",
"scheme": "MetaMask",
"configuration": "Debug",
"device": "iPhone-16-Pro",
"buildCommand":"yarn start:ios",
"binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/MetaMask.app"
},
"android": {
"packageName": "com.metamask",
"buildType": "Debug",
"binaryPath": "android/app/build/outputs/apk/prod/debug/app-prod-debug.apk"
},
"debug": true,
"report": true
}
- 主要语言
- TypeScript
- 星标
- 693
- 派生
- 27
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
FormidableLabs/react-native-owl 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 5/100
FormidableLabs/react-native-owl#194 · 3 条评论 · 1 个 reaction ·
-
bug
难度 3/5 1-2 天 新手友好度 42/100
FormidableLabs/react-native-owl#191 · 3 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 30/100
FormidableLabs/react-native-owl#190 · 1 条评论 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 30/100
FormidableLabs/react-native-owl#186 · 1 条评论 · 1 个 reaction ·
-
难度 5/5 一周以上 新手友好度 20/100
查看 FormidableLabs/react-native-owl 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
Automattic/data-liberation-agent#953 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 90/100
funmary-app/funmary#399 ·
维护者通常 1 天内回复
-
area:curator enhancement
难度 2/5 1-3 小时 新手友好度 74/100
CassioDalla/Scrinalia#150 ·
维护者通常 1 天内回复
-
status: needs-triage v1-bug-bash
难度 2/5 1-3 小时 新手友好度 82/100
a2ui-project/a2ui#3533 ·
维护者通常 1 天内回复
-
backend enhancement priority:P3
难度 2/5 1-3 小时 新手友好度 78/100
geolens-io/geolens#3310 ·
维护者通常 1 天内回复