Nativescript-cli: applyPluginsCocoaPods fails on case sensitive volumes

Created on 23 Nov 2019  ยท  3Comments  ยท  Source: NativeScript/nativescript-cli

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.2.2
  • Cross-platform modules: 6.2.1
  • Android Runtime: 6.2.0
  • iOS Runtime: 6.2.0
  • Plugin(s):

$ tns plugin list Dependencies: โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ Plugin โ”‚ Version โ”‚ โ”‚ nativescript-vue โ”‚ ^2.4.0 โ”‚ โ”‚ tns-core-modules โ”‚ ^6.2.1 โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ Dev Dependencies: โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ Plugin โ”‚ Version โ”‚ โ”‚ @babel/core โ”‚ ^7.0.0 โ”‚ โ”‚ @babel/preset-env โ”‚ ^7.0.0 โ”‚ โ”‚ babel-loader โ”‚ ^8.0.2 โ”‚ โ”‚ nativescript-dev-webpack โ”‚ ^1.0.0 โ”‚ โ”‚ nativescript-vue-template-compiler โ”‚ ^2.0.0 โ”‚ โ”‚ nativescript-worker-loader โ”‚ ~0.9.0 โ”‚ โ”‚ node-sass โ”‚ ^4.9.2 โ”‚ โ”‚ vue-loader โ”‚ ^15.4.0 โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Describe the bug
File: NativeScript/nativescript-cli/blob/master/lib/services/ios-project-service.ts
Method: applyPluginsCocoaPods
Line https://github.com/NativeScript/nativescript-cli/blob/master/lib/services/ios-project-service.ts#L833

This method checks for the pluginPlatformsFolderPath using the normalizedPlatformName which is iOS

In reality the folder names are lowercase:

Example of a plugin:

To Reproduce

  1. Create a new project on a case sensitive drive
  2. run tns platform add ios
  3. run tns prepare ios

Plugin Podfiles are not added.

Expected behavior

Plugin Podfile should be included

bug ios CocoaPods

Most helpful comment

Hey @leevigraham ,
Thanks for reporting this issue. A fix is available in our next version and should be live when we release 6.3.0 release.
Meanwhile you can give it a try by installing the next version of CLI: npm i -g nativescript@next.

All 3 comments

Looks like @Fatme and @KristianDD worked on some of this code.

Hey @leevigraham ,
Thanks for reporting this issue. A fix is available in our next version and should be live when we release 6.3.0 release.
Meanwhile you can give it a try by installing the next version of CLI: npm i -g nativescript@next.

Was this page helpful?
0 / 5 - 0 ratings