Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump up to new SDK (3.3) - causing issues? #1

Closed
jlooper opened this issue Jul 9, 2016 · 3 comments
Closed

Bump up to new SDK (3.3) - causing issues? #1

jlooper opened this issue Jul 9, 2016 · 3 comments

Comments

@jlooper
Copy link

jlooper commented Jul 9, 2016

When simply cloning this repo and following the instructions, I get the following error. Note, I'm on 0.39.0 cocoapods version, per our understanding that this is needed. Is there some old version of Firebase that I should uninstall? Yikes!

LOOPERMAC:Firebase Looper$ tns run ios --emulator
Executing before-prepare hook from /Users/Looper/Desktop/nativescript-plugin-firebase-demo-master/Firebase/hooks/before-prepare/nativescript-dev-typescript.js
Found peer TypeScript 1.8.10
Failed to find LaunchScreen.storyboard but it was specified in the Info.plist.
Consider updating the resources in app/App_Resources/iOS/.
A good starting point would be to create a new project and diff the changes with your current one.
Also the following repo may be helpful: https://github.com/NativeScript/template-hello-world/tree/master/App_Resources/iOS
We will now place an empty obsolete compatability white screen LauncScreen.xib for you in platforms/ios/Firebase/Resources/LaunchScreen.xib so your app may appear as it did in pre v2.1.0 versions of the ios runtime.
The iOS Deployment Target is now 8.0 in order to support Cocoa Touch Frameworks in CocoaPods.
Successfully prepared plugin nativescript-plugin-firebase for ios.
Successfully prepared plugin tns-core-modules for ios.
The iOS Deployment Target is now 8.0 in order to support Cocoa Touch Frameworks.
Successfully prepared plugin tns-core-modules-widgets for ios.
Installing pods...
Updating local specs repositories

CocoaPods 1.0.1 is available.
To update use: `gem install cocoapods`
Until we reach version 1.0 the features of CocoaPods can and will change.
We strongly recommend that you use the latest version at all times.

For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Firebase/Database (~> 3.3)` required by `Podfile`
Processing node_modules failed. Error: Command sandbox-pod failed with exit code 1 Error output: 
 [!] Unable to load a specification for the plugin `/Library/Ruby/Gems/2.0.0/gems/cocoapods-deintegrate-1.0.0`

[!] CocoaPods was not able to update the `master` repo. If this is an unexpected issue and persists you can inspect it running `pod repo update --verbose`

Sending exception report (press Ctrl+C to stop).....
@jlooper
Copy link
Author

jlooper commented Jul 9, 2016

Putting the solution here, in case of problems for others!

You need to get rid of any older installation of a Firebase SDK on your system before you can install a new one. Normally to do this, you can go to /platforms/ios and hit pod repo update --verbose. For me, this was failing because there were some rogue, untracked pods in my /Specs folder.

Using the --verbose flag, you can see which ones they are, and remove them manually:
For me they were:

Updating spec repo `master`
  $ /usr/local/bin/git pull --ff-only
  error: The following untracked working tree files would be overwritten by merge:
    Specs/JLCustomImagesViewerView/1.0.0/JLCustomImagesViewerView.podspec.json
    Specs/PJFDataSource/1.0.0/PJFDataSource.podspec.json
    Specs/Spotify-iOS-SDK/0.16.1/Spotify-iOS-SDK.podspec.json
  Please move or remove them before you can merge.
  Aborting
  Updating 3c20e73..89624d8

Once I removed these folders, I hit pod install and the entire repo is updated via Git, installing Firebase 3.3.0.

Hope this will help others.

@EddyVerbruggen
Copy link
Owner

@jlooper Do you feel like this is something for the readme? I'm a little hesitant since this can happen to any pod-powered plugin..

@jlooper
Copy link
Author

jlooper commented Jul 10, 2016

I'm going to post it to my personal blog, no worries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants