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.

Sign up for GitHub

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

Jump to bottom

make run-ios-device DEVICE_NAME="YOUR DEVICE NAME" fails while building with error code 65 #16310

Closed
siddarthkay opened this issue Jun 19, 2023 · 7 comments · Fixed by #18845
Closed

make run-ios-device DEVICE_NAME="YOUR DEVICE NAME" fails while building with error code 65 #16310

siddarthkay opened this issue Jun 19, 2023 · 7 comments · Fixed by #18845
Labels
ios

Comments

@siddarthkay
Copy link
Contributor

Bug Report

Problem

As reported first by @Parveshdhull and then by @igor-sirotin

  • make show-ios-devices : gives the name of attached iPhone properly
  • when using the name of the connected iPhone like this : make run-ios-device DEVICE_NAME="YOUR DEVICE NAME" causes iOS build to fail with error code 65.

Screenshots

igor-ios-error
@ibrkhalil
Copy link
Contributor

Can you retry with node v16.16.0?

@siddarthkay
Copy link
Contributor Author

@ibrkhalil : we use these commands within nix context and we set nodejs version here
https://github.com/status-im/status-mobile/blob/develop/nix/overlay.nix#L61
which is set to v18.

This issue is not node specific since it works on both my old and my new macbook.
Its probably something else.

@ibrkhalil
Copy link
Contributor

@ibrkhalil : we use these commands within nix context and we set nodejs version here https://github.com/status-im/status-mobile/blob/develop/nix/overlay.nix#L61 which is set to v18.

This issue is not node specific since it works on both my old and my new macbook. Its probably something else.

Hmmm, I had the same exact issue two days ago when building on a physical device.
What I did was use nvm to use node 16 and made sure that the development team settings on XCode are done correctly.
And when selecting a project file make sure to use the one with the .xcodeproj extension inside status-mobile/ios

@siddarthkay
Copy link
Contributor Author

siddarthkay commented Jun 20, 2023 •
edited
Loading

Thanks @ibrkhalil : I'll try recreating this locally, and if nvm is indeed being preferred over nix then that is a bigger problem to solve.
Thanks for sharing!

@siddarthkay
Copy link
Contributor Author

siddarthkay commented Jun 20, 2023 •
edited
Loading

@ibrkhalil : just to follow up on what you did, were you able to finally deploy on your physical iOS device using Xcode.app or using make run-ios-device command?

@ibrkhalil
Copy link
Contributor

@ibrkhalil : just to follow up on what you did, were you able to finally deploy on your physical iOS device using Xcode.app or using make run-ios-device command?

make run-ios-device

@siddarthkay
Copy link
Contributor Author

update : This issue was automatically fixed for @Parveshdhull right after he updated his macbook to latest update :)
I have not yet tried to recreate this but will try to do so next week.

@cammellos cammellos added bug and removed bug labels Jul 14, 2023
@siddarthkay siddarthkay mentioned this issue Feb 15, 2024
Merged
siddarthkay added a commit that referenced this issue Feb 16, 2024
@siddarthkay
fix: make run-ios-device script
f9c4935 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script
8962eb0 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script
0f0ff6f 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script
c9632b8 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script
b048973 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

we also set up a logs folder and add a Readme

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script
43eaa57 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.

we also set up a logs folder and add a Readme

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)
siddarthkay added a commit that referenced this issue Feb 20, 2024
@siddarthkay
fix: make run-ios-device script (#18845)
5a7bfc6 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.
We also set up a logs folder and add a Readme.

## Review notes

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)

## Platforms
- iOS
ibrkhalil pushed a commit that referenced this issue Feb 25, 2024
@siddarthkay @ibrkhalil
fix: make run-ios-device script (#18845)
1277877 
fixes #16310

We used to reply on `react-native cli` and would pass a `--device` flag to deploy the debug variant of `iOS` app on connected `iPhone`.
`react-native cli` under the hood uses `ios-deploy` library to achieve this functionality.
This showed many weird issues, specifically in locating connected devices and failures at build step with ambiguous error messages.

This commit fixes it by using our custom script `run-ios-devices.sh` which does not rely on `ios-deploy`.
We use `libimobiledevice` to identify `UDID` of a connected `iPhone`.
We use `xcrun devicectl device install app` and `xcrun devicectl device process launch` to install and launch the app.

This works well with `Xcode 15` and `iOS 17.x`.
We can now remove `ios-deploy` from `iOS` shell and `nix` overlay.
We also set up a logs folder and add a Readme.

## Review notes

- connect your iPhone to your Laptop via a cable
- `make run-clojure`
- `make run-ios-device`
(note: no need to pass device name now)

## Platforms
- iOS
@ilmotta ilmotta removed the bug label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ios
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: make run-ios-device script status-im/status-mobile
4 participants
@ilmotta @cammellos @ibrkhalil @siddarthkay