Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Can you make the errors logs a bit clearer?

Abierto
  • ¿Algo no está bien?
#188 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
android, ios, react-native, typescript
Área
documentation, mobile, testing

Línea de trabajo

Empieza reproduciendo los fallos reportados de yarn owl test --platform ios y de Android ./gradlew assembleDebug --console plain -PisOwlBuild=true con la configuración de Owl proporcionada. Rastrea cómo estos comandos informan de los errores y revisa la documentación de configuración de Android; se considera terminado cuando los logs son más accionables y la configuración de Android documentada refleja el proceso requerido.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
  }
Lenguaje dominante
TypeScript
Estrellas
694
Forks
27
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FormidableLabs/react-native-owl

Todos los issues de FormidableLabs/react-native-owl

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.