NativeScript / NativeScript/nativescript-cli
iOS simulator can't find app because incorrect case of "Build" in path
@endarova arbeitet bereits daran.
Seit 18.11.2019.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 1.1k
- Forks
- 204
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 8
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?
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.
Bewertung
Dieses Issue wurde noch nicht bewertet.