Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[error] Couldn't start device session Command was killed with SIGABRT (Aborted) #405

Open
timonjagi opened this issue Jun 25, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@timonjagi
Copy link
Collaborator

Android build on React Native IDE is successful but i get the error on the React Native IDE logs :

[error] Couldn't start device session Command was killed with SIGABRT (Aborted): /Users/timothy/.vscode/extensions/swmansion.react-native-ide-0.0.15-darwin-arm64/dist/sim-server-executable android emulator-5554

When I run the project directly on the Android emulator it works as expected.

Environment:

React Native IDE: v0.0.15
React Native: 0.74.1
Expo: ^51.0.8
Expo Router: ~3.5.14

Logs:

2024-06-25 10:48:01.941 [info] Starting Android build
2024-06-25 10:48:12.820 [info] Emulator output INFO    | Boot completed in 24655 ms
2024-06-25 10:48:12.820 [info] Emulator output INFO    | Increasing screen off timeout, logcat buffer size to 2M.
2024-06-25 10:55:24.993 [info] Android build sucessful
2024-06-25 10:55:35.479 [info] Launch preview /Users/timothy/.vscode/extensions/swmansion.react-native-ide-0.0.15-darwin-arm64/dist/sim-server-executable android,emulator-5554
2024-06-25 10:55:35.479 [info] Will wait for app ready and for preview
2024-06-25 10:55:36.398 [info] Subprocess /Users/timothy/.vscode/extensions/swmansion.react-native-ide-0.0.15-darwin-arm64/dist/sim-server-executable was terminated with SIGABRT
2024-06-25 10:55:36.402 [error] Couldn't start device session Command was killed with SIGABRT (Aborted): /Users/timothy/.vscode/extensions/swmansion.react-native-ide-0.0.15-darwin-arm64/dist/sim-server-executable android emulator-5554
2024-06-25 10:56:27.687 [info] Metro Android Bundled 43598ms node_modules/expo-router/entry.js (2504 modules)
2024-06-25 10:56:30.053 [info] Devtools client connected
2024-06-25 10:56:32.226 [info] Metro  LOG  Running "main" with {"rootTag":11} http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 17374 22
2024-06-25 10:56:32.402 [info] App ready
2024-06-25 10:56:32.462 [info] Metro  LOG  setting up translations http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 177709 15
2024-06-25 10:56:32.624 [info] Metro  LOG  local locale: en-US  http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 177710 15
2024-06-25 10:56:32.657 [info] Metro  LOG  default locale: en-US  http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 177711 15
2024-06-25 10:56:32.705 [info] Metro  LOG  write to storage locale: en-US http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 177732 17
2024-06-25 10:56:32.740 [info] Metro  LOG  getting locale from storage and writing it to memory en-US http://localhost:49676/node_modules/expo-router/entry.bundle//&platform=android&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app 177723 17
@timonjagi timonjagi added the bug Something isn't working label Jun 25, 2024
@jakub-gonet
Copy link
Member

That's interesting. It means that our simulator streaming server crashed for some reason. Do you have a project that reproduces it and you can share it by any chance?

@timonjagi
Copy link
Collaborator Author

Hey @jakub-gonet, thanks for looking into this.

Here is a project that reproduces the issue.

@jakub-gonet
Copy link
Member

Seems like this is problem with environment, it loads the app on my machine. Will look into streaming server.
image

@jakub-gonet
Copy link
Member

Do you have any custom setup for android? Things like running different arch simulators, non-default locations for android directories, etc?

@timonjagi
Copy link
Collaborator Author

No, my android setup is pretty much the default.

@CamBowes
Copy link

CamBowes commented Jul 7, 2024

+1 - getting this on Android and iOS Sims, using Expo 51 project on the MacOS Sequoia beta

@ddnzcn
Copy link

ddnzcn commented Jul 8, 2024

+1 getting this on fresh expo cli app both ios and android simulators not working

@corasan
Copy link
Collaborator

corasan commented Jul 14, 2024

+1 Getting the same error on expo SDK 51 after installing to MacOS Sequoia beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants