ProgressNS / sidekick-feedback

This repository is for feedback regarding NativeScript Sidekick. Use the issues system here to submit feature requests or vote for existing ones.
45 stars 9 forks source link

Launching Debugger on iPhone from Cloud Build #424

Open jandmslaven opened 5 years ago

jandmslaven commented 5 years ago

I am using NativeScript CLI 6.1.2 When try to run my application on a physical device (iPhone 6s running iOS 13.1) the application builds on the cloud successfully and installs. LiveSync and debugger fail with the following error:

[19-09-23 12:51:44.448] (CLI) Unable to apply changes on device: 5e4b738e6530dfac2c03021ddbb196eacaa1945b. Error is: Could not start house arrest for application . [19-09-23 12:51:44.451] Error detected during LiveSync on 5e4b738e6530dfac2c03021ddbb196eacaa1945b for . Error: Could not start house arrest for application [19-09-23 12:51:44.458] Stopped LiveSync on 5e4b738e6530dfac2c03021ddbb196eacaa1945b for . [19-09-23 12:51:44.460] Couldn't enable debugging for 5e4b738e6530dfac2c03021ddbb196eacaa1945b, Error: Couldn't enable debugging for 5e4b738e6530dfac2c03021ddbb196eacaa1945b

NickIliev commented 5 years ago

@jandmslaven, there might be a lot of reasons that are causing the app to fail on a real device. Are you building in release? Have you signed the app with the proper provisioning profile? Are you using some plugins that are requiring special configs?

Also after the app installs - are you able to start the app manually (by tapping the icon on the device)?

Notice that you can't start an app on a real iOS device without having a proper provisioning profile provided. If that is not the issue then I recommend creating a clean rebuild (check the clean option from the build menu)

jandmslaven commented 5 years ago

I discovered that the nativescript-pro-ui plug does not work with NativeScript CLI 6.1.2 on iOS devices. Interestingly it works just fine on Android devices. I dropped that plug-in and installed it's replacement nativescript-sidedrawer instead, refactored my code, and the app was installable on iOS devices again. Thanks for looking in to the problem.

AliKalkandelen commented 5 years ago

Im having the same issue, except i dont even have nativescript-pro-ui.

heres my package.json

"nativescript": {
    "id": "com.transperfect.projectamobileapp",
    "tns-ios": {
      "version": "6.1.0"
    },
    "tns-android": {
      "version": "6.1.1"
    }
  },
  "dependencies": {
    "@angular/animations": "^8.2.9",
    "@angular/common": "^8.2.9",
    "@angular/compiler": "^8.2.9",
    "@angular/core": "^8.2.9",
    "@angular/forms": "^8.2.9",
    "@angular/platform-browser": "^8.2.9",
    "@angular/platform-browser-dynamic": "^8.2.9",
    "@angular/router": "^8.2.9",
    "nativescript-angular": "~8.2.0",
    "nativescript-iqkeyboardmanager": "~1.3.0",
    "nativescript-pdf-view": "~2.0.1",
    "nativescript-theme-core": "~1.0.6",
    "nativescript-ui-calendar": "5.0.0",
    "nativescript-ui-listview": "7.0.0",
    "reflect-metadata": "~0.1.12",
    "rxjs": "^6.4.0",
    "tns-core-modules": "~6.1.0",
    "zone.js": "~0.9.1"
  },
  "devDependencies": {
    "@angular/compiler-cli": "^8.2.9",
    "@ngtools/webpack": "^8.2.2",
    "codelyzer": "^5.1.2",
    "nativescript-dev-webpack": "^1.2.1",
    "node-sass": "^4.12.0",
    "sass-loader": "^8.0.0",
    "tns-platform-declarations": "6.0.1",
    "tslint": "~5.11.0",
    "typescript": "~3.5.3"
  },

@NickIliev to answer your questions im running in cloud, debug, with webpack and hot module replacement turned on. Clean rebuild also gives same problem.

After livesync fails im able to start the app manually by tapping on the icon.

I think i have the right provisioning file. How would i check for that?

NickIliev commented 5 years ago

@AliKalkandelen what is the version of iOS that is installed on your real device? Make sure you are not using a beta version and that your device is using the latest official iOS (13.1.3) - if an update is needed make a clean rebuild of the app after the OS update is over.

AliKalkandelen commented 5 years ago

@NickIliev I am on an Iphone 11 running IOS 13.1.13(17A878) atm. Is there a way i can debug this error?