Geofire Cocoapod 2.0 Isn't Available

[psopher]

Hi,

I'm just confused because the ReadMe says I can download the Geofire 2.0 Cocoapod, but when I try to do it, I get this message:

None of your spec sources contain a spec satisfying the dependency: GeoFire (~> 2.0).

And when I look at the page on the CocoaPod website, it says version 1.1.3 is the latest one.

Is this on purpose? When will the cocoapod be ready for this newest version of Geofire?

[jwngr]

The 2.0 branch just got merged in yesterday and we are still working on getting out the pod. Hang tight. It should be out later today.

[greggmojica]

@jwngr Looking forward to it!

[greggmojica]

Is this still being updated today? Sorry, but I have an app that relies on this.... @jwngr

[mcmarshall]

Watching this, too! Glad this post was here...wasn't working for me!

Very excited for this...thank you!!!

[jwngr]

We are still working through some CocoaPods issues.

@greggmojica - There's a perfectly usable 1.1.3 version of the GeoFire CocoaPod that you can use. This should not be blocking your app.

[asciimike]

It's an open source project as well, so folks are welcome to use it as a local spec--you're not even blocked on using the new version locally (or even shipping like this!)

pod 'GeoFire', :path => 'path/to/local/geofire/directory'

[mcmarshall]

Running it locally gives me a build error saying "Module Firebase not found."

I'm a novice but the directions seem pretty straightforward. I'll wait for the cocoa pods, but just found it interesting I'm getting an error and you seem to be having trouble...

[sentiasa]

@jwngr Please let us know here when it is out. Do you think it will be out today?

[mcmarshall]

If anyone else was having that "Firebase module not found issue" - in the two places it identified errors, I replaced "@import Firebase;" with the line suggested here, and it worked: http://stackoverflow.com/questions/37322473/firebase-module-install-on-ios#comment62164478_37322473

[mcmarshall]

Really no reason to wait on this. Download it to your machine and use the "path" to point to it. I have 2.0 working fine. Whenever it hits cocoa pods, I'll just switch the line in the pod file.

[mpcmarques]

Im having a error at "@import Firebase;" in Geofire.m

[mcmarshall]

@mpcmarques See my post above...I was having trouble posting the exact line to change that to (twice) but the link I posted has it

[mcmarshall]

@greggmojica Seriously, it is incredibly easy to install locally. I am an extreme(!) novice and I got it working. No reason to have any delay based on this. Download it, add the location of the folder to the pod file (using that "path" thing mentioned above), then (for me) fix that import error twice.

And I have 2.0 working.

[zgosalvez]

I'm experiencing multiple errors with the "workaround". Really hoping we could get an official version out.

---

1st. Update the Podfile:

//...
pod 'Firebase'
pod 'Firebase/Core'
pod 'Firebase/Database'
pod 'Firebase/Auth'
pod 'GeoFire', :git => 'https://github.com/firebase/geofire-objc.git'
// ...

2nd. pod install
"Module 'Firebase' not found" error on the following files:

• GeoFire.m
• GFQuery.m

3rd. Replace @import Firebase; with #import <Firebase/Firebase.h>. This really shouldn't be the fix, since it reverts the instructions on Upgrade your iOS app from Firebase.com.
4th. Build issues:

[mcmarshall]

@zgosalvez my path in the pod file is a local folder. I downloaded the zip of geofire, unzipped, and used the path for that folder. (Dragged onto the open pod file to get its full path.)

[zgosalvez]

@mcmarshall Did it your way, still no cigar; shows the same issues I stated. Thanks for the tip anyway.

[callam]

Is there a fix for this? I have the pods Firebase 3.2.1 and GeoFire 2.0.0 via git installed however I am getting errors in GeoFire.h and GFQuery.h saying Module 'Firebase' not found.

I have tried replacing @import Firebase with #import <Firebase/Firebase.h>, but this brings on more errors, the same errors that are in the screenshot from @zgosalvez

[fredericdnd]

I use Firebase 3.2.1 from Cocoapods, and have GeoFire 2.0.0 working on Swift ! Just download GeoFire project from GitHub website, drag and drop GeoFire sources into my project and create a Bridging-Header to import "GeoFire.h", and all is working great ;)

[manticarodrigo]

Hey @fredericdnddev. What do you mean by "sources" specifically if you don't mind me asking? Also, in the bridging header, do you write #import <GeoFire/GeoFire.h>?

[fredericdnd]

Hey @manticarodrigo, sorry, I mean the GeoFire folder containing the API and Implementation folders, and the .pch file. Drag the GeoFire folder into your project and select "Create groups" instead of "Create folder references", all the GeoFire files will be at the root of your project, so you can just import it in your bridging header with : #import "GeoFire.h"

[fredericdnd]

And I forgot one thing, you'll got an error saying that 'GeoFire/GeoFire.h' file is not found, so just replace the #import line with that of your bridging header, because GeoFire.h is no longer in the GeoFire folder, but at the root of your project

[manticarodrigo]

You drag the entire "GeoFire" folder containing those things, or the contents inside the folder? I am still getting the "Use of unresolved identifier "GeoFire" warning.

[fredericdnd]

1- drag the folder "GeoFire" into your project in Xcode
2- it will show you a pop-up "Choose options for adding theses files", select "Create groups" instead of "Create folder references"
3 - in your bridging-header, add the line #import "GeoFire.h"
4 - If you run your project know, you will get the error 'GeoFire/GeoFire.h' file not found, so click on the error, and in the displayed file, replace #import <GeoFire/GeoFire.h> with #import "GeoFire.h"

Have you added your Bridging-Header in Build Settings ?

[manticarodrigo]

Thank you! I'll let you know if it works when Game of Thrones is over!

[fredericdnd]

No problem, good episode ;)

[manticarodrigo]

I hadn't added the bridging header to build settings. You're a life saver @fredericdnddev! Great episode btw.

[JingweiTu]

Can Firebase get the cocoapod version working, please? I keep getting the same issues, and the solution posted by @fredericdnddev didn't work for me (a lot of other errors showed up regarding GeoFire.m). I'd very much like to use this framework!

[cxt9]

I'm getting that while using the local path to the latest version I just downlaoded:

/iosprojects/project name/Pods/Headers/Private/Firebase/Firebase.h:1:9: 'FirebaseAnalytics/FirebaseAnalytics.h' file not found

I can't change the file (locked and can't unlock it) so no way to try and fix it.

[jerembab]

@ripkaskalalaz nice , thanks for the fast reply

[brunocortes06]

My xcode dont show into Pods my firebase framework, what is wrong?

[AJMiller]

@brunocortes06 if you are using Firebase 3.8.0+ then make sure you modified your post_install section to follow @programmerdave version above: #48 (comment)

[brunocortes06]

@AJMiller my firebase is 3.3.0

my paths seems to be correct too

and i tried this post install, continue having a .xcconfig file in Pods section

[AJMiller]

@brunocortes06 that is totally normal. Take a look at my fully functioning firebase/geofire based app

[mjpablo23]

Summary as described by zgosalvez: if compiler doesn't find FirebaseDatabase.h: Select FirebaseDatabase.framework from Pods->Pods->FirebaseDatabase->Frameworks->FirebaseDatabase.framework, open right panel, select GeoFire for Target Membership

[grantkemp]

Any Idea if this is on the roadmap to be fixed.. ?

[chigogiggs]

go to 'Pods', then got the new 'pod' folder in the original 'pod' folder, then go to 'firebasedatase' folder, go to frameworks, then click on 'FirebaseData...se.framework'. on the right side menu check 'goofier' and build. works! ur welcome

[moazkh60]

Still waiting for the pod. Any updates ?

[yarodevuci]

is any way to install 2.0 manually ?

[asciimike]

The answer is that you'll want to use the open source version of the Firebase SDK, which won't have these issues.

I can change GeoFire.podspec to reference the FirebaseCommunity/Database pod subspec, but since that one isn't published (and I'm not sure that we can reference an unpublished podspec e.g. via git), I don't know if it will work properly. This means I'll either have to publish the FirebaseCommunity pod, or remove the dependency and have them be peers (make every reference in GeoFire weak).

[grantkemp]

@moazkh60 @yarodevuci It takes roughly two minutes to copy it manually. If you get stuck - happy to share a video of how to do it. Is there a nice simple "Hello World" app for Geofire? if not - I can spin up one with a Geofire Client

[moazkh60]

@grantkemp I know I already did and now I am using it but still It would be great if they release the pod.

[asciimike]

Turns out the pod is released, it just doesn't work the same way as the Firebase pod. See #95, which depends on the FirebaseCommunity pod, and should solve these problems. I'll verify and deploy it if it works.

[fvisticot]

Any update ? would be fine to use this pod 'as is' without any tricks

[asciimike]

I believe things are "Just Working" in CocoaPods 1.4.x (still in beta).

You can install the beta version of CocoaPods via: sudo gem install cocoapods --pre

The following Podfile worked for me:

target 'geofire-test' do
  use_frameworks!

  pod 'Firebase/Auth'
  pod 'GeoFire' 
end

[bbookman]

What is the latest?

[asciimike]

@bbookman now that CocoaPods 1.4 is live, sudo gem install cocoapods and install it as you would any other pod.

[borut-t]

I've just installed the latest version with cocoapods pod 'GeoFire' and it works.
@jwngr that's hilarious you cannot prepare a proper release, update Readme and close this dated issue already 😞

[jwngr]

@borut-t - I haven't worked at Google / Firebase for several years, so there's not much I can do at this point. Have a good day.

[borut-t]

@jwngr I didn't want to point at you. I've just read the responses and you were the one responding to questions. Sorry about that, I was just angry about the current state.

[asciimike]

I'm confused, it works now, right? We just forgot to close the issue?

[borut-t]

@mcdonamp I was confused too. It works now yes.