search

nabil-mansouri / nativescript-nbmaterial

27 stars 5 forks source link

Unmet Dependency #4

Open Tyg-g opened 6 years ago

Tyg-g commented 6 years ago

I'm trying to use the nativescript-nbmaterial-elevation module, I get this:

$ npm i nativescript-nbmaterial-elevation --save
/media/dolgok/tmp/prog/veg-ns
├─┬ nativescript-nbmaterial-elevation@1.0.1 
│ ├── nativescript-nbmaterial-commons@1.0.0 
│ ├─┬ nativescript-nbmaterial-layouts@1.0.1 
│ │ └── UNMET PEER DEPENDENCY tns-core-modules@^3.0.0
│ └── UNMET PEER DEPENDENCY tns-core-modules@^3.0.0
└── UNMET PEER DEPENDENCY tns-core-modules@4.1.0

npm WARN nativescript-nbmaterial-elevation@1.0.1 requires a peer of tns-core-modules@^3.4.1 but none was installed.
npm WARN nativescript-nbmaterial-layouts@1.0.1 requires a peer of tns-core-modules@^3.4.1 but none was installed.
npm WARN nativescript-nbmaterial-commons@1.0.0 requires a peer of tns-core-modules@^3.0.0 but none was installed.
Tyg-g commented 6 years ago

I'm trying hard to use this plugin but no success. Now I don't know if it's because of the dependency problems or something else. We really need better documentation with usage samples. This plugin would be super useful for me and others, too, I guess. :)

damianocorrado commented 6 years ago

I have the same problem, seems that this plugin is not compatible with newer version of tns-core-modules (in my case not work with tns-core-modules ^4.1.0)

npm WARN nativescript-nbmaterial-bottomsheet@1.0.0 requires a peer of tns-core-modules@^3.4.0 but none is installed. You must install peer dependencies yourself. npm WARN nativescript-nbmaterial-commons@1.0.0 requires a peer of tns-core-modules@^3.0.0 but none is installed. You must install peer dependencies yourself. npm WARN nativescript-nbmaterial-elevation@1.0.1 requires a peer of tns-core-modules@^3.4.1 but none is installed. You must install peer dependencies yourself. npm WARN nativescript-nbmaterial-layouts@1.0.1 requires a peer of tns-core-modules@^3.4.1 but none is installed. You must install peer dependencies yourself.

This plugin would be super useful but actually is inusable. Please fix it. Thank you.

chrishaff commented 6 years ago

I got the same issues on iOS. Works fine on Android.

On iOS once I make it past the dependencies I get a compile error about the Swift version. I tried going back to XCode 8.1 and updating the Swift version for the project, but that does not fix it.

chrishaff commented 6 years ago

I changed the dependencies in package.json to "tns-core-modules": "^4.2.0". This clears up the issues @Tyg-g and @damianocorrado reported.

Next I got Swift Version issues. For that I installed the {N} plugin https://github.com/naderio/nativescript-swift-3.0.

Now the issue is this: ld: warning: directory not found for option '-F/Users/chrishaff/Library/Developer/Xcode/DerivedData/tabtest-ckkggclfefcohsduaefatpbpguvy/Build/Products/Debug-iphonesimulator/CCBottomRefreshControl' ld: warning: directory not found for option '-F/Users/chrishaff/Library/Developer/Xcode/DerivedData/tabtest-ckkggclfefcohsduaefatpbpguvy/Build/Products/Debug-iphonesimulator/DelegateProxy' ld: warning: directory not found for option '-F/Users/chrishaff/Library/Developer/Xcode/DerivedData/tabtest-ckkggclfefcohsduaefatpbpguvy/Build/Products/Debug-iphonesimulator/MaterialComponents' ld: framework not found CCBottomRefreshControl clang: error: linker command failed with exit code 1 (use -v to see invocation)

That directory does indeed not exist. This is despite in pod being installed just fine. At this point I tried to remove the dependency on the CCBottomRefreshControl (don't need it) but it seems to be pretty baked in.

@nabil-mansouri Any pointers? This great lib you created is non-functional on iOS.

nabil-mansouri commented 6 years ago

Hello guys Sorry I am very busy on theses days. I think it is a nativescript / pod issue. I will try to install it on tns4 to check whether I need to upgrade it. I don’t think that nativescript has changed the plugin architecture but I will check. Can you confirm that it is not working if you

chrishaff commented 6 years ago

@nabil-mansouri

  1. I can confirm that the three steps you outline do not resolve the issue.
  2. I checked the docs and release notes. There seem to be no changes for the plugin architecture. You should probably check for yourself though.
  3. There is a fine point in that once I am past the initial hurdles an error occurs during the Xcode build.

Thanks!