iOS simulator can't find app because incorrect case of "Build" in path
@endarova arbeitet bereits daran.
Seit 18.11.2019.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
- CLI: 6.1.2
Describe the bug
Trying to migrate a project from 5.4 to 6 and having trouble running on the iOS emulator due to case sensitivity of the build path. Seems like 5.4 used 'build' but 6 changed this to 'Build'.
Replicate
tns platform remove ios
tns platform add ios
tns run ios --emulator
I get:
Project successfully built.
The build result is located at: /Users/npn/Development/ns6/test/platforms/ios/build/Debug-iphonesimulator/test.app
Installing on device 84F073AE-D836-4C81-8803-FDA3ABC8C731...
Unable to apply changes on device: 84F073AE-D836-4C81-8803-FDA3ABC8C731. Error is: Command xcrun with arguments simctl install 84F073AE-D836-4C81-8803-FDA3ABC8C731 /Users/npn/Development/ns6/test/platforms/ios/build/Debug-iphonesimulator/test.app failed with exit code 2. Error output:
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Expected
The issue is in the case of the word build in the path. On my drive tns is creating
/Users/npn/Development/ns6/test/platforms/ios/Build/Debug-iphonesimulator/test.app
but it's giving args to simctl as
/Users/npn/Development/ns6/test/platforms/ios/build/Debug-iphonesimulator/test.app
Other than manually adjusting the path on my file system how do I get the two to agree on the case?
- Vorherrschende Sprache
- JavaScript
- Sterne
- 1.1k
- Forks
- 204
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 8
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus NativeScript/nativescript-cli
-
in-progress
NativeScript/nativescript-cli#6140 · 2 Kommentare · 1 zugewiesene Person ·
-
NativeScript/nativescript-cli#6090 · 1 zugewiesene Person ·
-
in progress
NativeScript/nativescript-cli#6015 · 1 Reaktion · 1 zugewiesene Person ·
-
question
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
NativeScript/nativescript-cli#5992 · 5 Kommentare ·
-
feature-pending-triage
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
NativeScript/nativescript-cli#5975 ·
Alle Issues in NativeScript/nativescript-cli
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
avniproject/avni-client#2135 ·
-
automated broken-link
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
bevyengine/bevy-website#2595 ·