NativeScript / NativeScript/ios
Cannot connect debugger to emulator with iOS13.7
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 150
- Forks
- 43
- Ø Merge
- 3 T. 10 Std.
- Gemergte PRs (30 T.)
- 22
Beschreibung
Hello together,
I am currently trying to debug an issue in my app which seems to be related to an older iOS version being used, seems like ngOnInit is not called for an angular component in my app. However, the issue I am reporting here is related to not being able to connect with the debugger to my emulator (iPhone SE (1st generation)) when iOS13.7 is used.
Successfully synced application de.mynutridiary.mnd on device C3683AA3-C313-44C2-A3B1-45D5DBBD7BF6.
Frontend client connected.
NativeScript debugger was not able to get inspector socket port on device C3683AA3-C313-44C2-A3B1-45D5DBBD7BF6 for application de.mynutridiary.mnd.
Cannot connect to device socket. The error message is 'Device socket port cannot be found.'.
This happens with
"@nativescript/ios": "8.5.2-alpha.2",
and 8.5.1
OS: macOS 13.2.1
CPU: (10) arm64 Apple M1 Pro
Shell: /bin/zsh
node: 18.12.1
npm: 8.19.2
nativescript: 8.5.3
# android
java: 11.0.18
ndk: Not Found
apis: Not Found
build_tools: Not Found
system_images: Not Found
# ios
xcode: 14.3/14E222b
cocoapods: 1.12.0
python: 3.11.2
python3: 3.11.2
ruby: 2.7.7
platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Dependencies
"dependencies": {
"@angular/animations": "15.2.7",
"@angular/common": "15.2.7",
"@angular/compiler": "15.2.7",
"@angular/core": "15.2.7",
"@angular/forms": "15.2.7",
"@angular/platform-browser": "15.2.7",
"@angular/platform-browser-dynamic": "15.2.7",
"@angular/router": "15.2.7",
"@apollo/client": "3.7.12",
"@mnd/external-web-view": "file:../mnd-plugins/dist/packages/external-web-view/mnd-external-web-view-1.0.0.tgz",
"@nativescript/angular": "15.2.0",
"@nativescript/core": "8.5.0",
"@nativescript/iqkeyboardmanager": "2.1.1",
"@nativescript/localize": "5.0.4",
"@nativescript/mlkit-barcode-scanning": "2.0.0",
"@nativescript/mlkit-core": "2.0.0",
"@nativescript/secure-storage": "3.0.0",
"@nativescript/theme": "3.0.2",
"@nativescript/ui-charts": "0.2.4",
"apollo-angular": "4.2.1",
"apollo3-cache-persist": "0.14.1",
"d3-ease": "3.0.1",
"graphql": "16.6.0",
"graphql-tag": "2.12.6",
"intl": "1.2.5",
"moment": "2.29.4",
"nativescript-health-data": "file:../mnd-custom-plugins/nativescript-health-data/publish/package/nativescript-health-data-2.0.0.tgz",
"nativescript-oauth2-ext": "file:../mnd-custom-plugins/nativescript-oauth2-ext/publish/package/nativescript-oauth2-ext-3.0.1.tgz",
"nativescript-sqlite": "2.8.6",
"nativescript-ui-calendar": "15.2.3",
"nativescript-ui-gauge": "15.2.3",
"rxjs": "7.8.0",
"uuid": "9.0.0",
"zone.js": "0.13.0"
},
"devDependencies": {
"@angular-devkit/build-angular": "15.2.6",
"@angular/compiler-cli": "15.2.7",
"@graphql-codegen/cli": "3.3.0",
"@graphql-codegen/fragment-matcher": "4.0.1",
"@graphql-codegen/introspection": "3.0.1",
"@graphql-codegen/typescript": "3.0.3",
"@graphql-codegen/typescript-apollo-angular": "3.5.6",
"@graphql-codegen/typescript-operations": "3.0.3",
"@nativescript/android": "8.5.0",
"@nativescript/ios": "8.5.2-alpha.2",
"@nativescript/types": "8.5.0",
"@nativescript/webpack": "5.0.14",
"@ngtools/webpack": "15.2.6",
"@types/d3-ease": "3.0.0",
"@types/intl": "1.2.0",
"@types/node": "18.15.11",
"@types/uuid": "9.0.1",
"keycloak-request-token": "0.1.0",
"rimraf": "5.0.0",
"sass": "1.62.0",
"ts-node": "10.9.1",
"typescript": "4.9.5"
}
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Im Issue werden keine Quelldateien oder Tests genannt. Beginnen Sie damit, den Fehler beim Debugger-Verbindungsaufbau mit den aufgelisteten @nativescript/ios-Versionen auf dem iPhone SE unter iOS 13.7 zu reproduzieren, und verfolgen Sie anschließend den Pfad „Device socket port cannot be found“. Erledigt ist die Aufgabe, wenn der Fehler behoben oder die Einschränkung der unterstützten Version dokumentiert ist.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript
- Bereich
- devtools, mobile-dev
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100