I use Geofire and FirebaseUI in my app.
In the documentation for how to upgrade to the new Firebase SDK, it says I need Geofire 1.2.x or beyond. However, this is not yet available in cocoapods. When will it be available?
Also, will I need to upgrade Firebase UI? How should I do that? It seems like a lot of the code for authentication is now outdated, so it would make sense that FirebaseUI would need to be upgraded.
Update
With FirebaseUI, I get this output in Terminal:
- `Firebase (~> 3.2)` required by `Podfile`
- `Firebase (~> 2.2)` required by `FirebaseUI (0.3.2)`
And with Geofire, I get this output in Terminal:
[!] Unable to satisfy the following requirements:
- `GeoFire (~> 1.2)` required by `Podfile`
You've got it spot on with Firebase update requirements for GeoFire, but for a "when"... well, as posted by David East of Firebase on GeoFire's github repo:
"Best estimate I can give you is that we will update GeoFire for iOS in the coming days to weeks. We've got a lot of open source libraries to update across a handful of languages, so it takes us time to make it all happen. Pull requests are always welcome if you want to give it a shot yourself!"
For now, if you're actively using GeoFire, I suggest just keeping Firebase at 2.5.1 and GeoFire at 1.1.3 and continue working until updates are pushed out. As for Firebase UI, it's different but documented here:
https://codelabs.developers.google.com/codelabs/firebase-ios-swift/index.html?index=..%2F..%2Findex#4
Hope this cleared things up. I was pretty frustrated with it as well.
Related
I've been trying to figure this out for several hours with no luck.
In older Flutter projects within Android Studio the Firebase Assistant appears in my Menu Tool-> Firebase; however, when I start new Flutter projects Firebase Assistant does not appear in the Tool's menu. Trying to open Firebase using search, produces a search result, but launching it fails (just an endless loading screen).
I've tried all of the listed items in these previously asked questions:
Firebase assistant not showing in Android Studio 3.4.1
Unable to find Tools > Firebase in Android studio 2.2.3
Firebase assistant not showing in Studio 2.2.3
I am using Android Studio 4.2.1
I've run updates on everything that I can think of to update.
The generally accepted answer in the previously asked questions referenced above is to ensure that the three Firebase plugins are enabled. I've verified that they are:
In older projects where Firebase Assistant appears in the Tools menu, if I disable the three plugins and restart, Firebase Assistant disappears from old projects. When I then re-enable them and restart, Firebase Assistant returns to the Tools menu in older projects. However, in a freshly created Flutter project, disabling and re-enabling the plugins does not cause Firebase Assistant to appear in the tools menu.
One person suggested making sure that you are logged into your Google account. I'm logged in, but that doesn't change anything.
I don't understand why it is available in old projects, but not in new projects.
I assume I'm simply overlooking something.
Any suggestions?
Thanks
EDIT:
Since posting this question, I have tried completely uninstalling Android Studio and performing a clean install of it, Flutter and Dart. However, I have the same result. Older projects have Firebase Assistant and new projects don't.
While trying to figure out the differences between the two projects in the hope of finding something which might explain why one project does have the Firebase Assistant available and new projects do not have Firebase Assistant available, despite having all the same plugins, build.gradle information and pubspec.yaml information, I happened to notice one difference.
In my older projects, the ones that have Firebase Assistant available, if I right click on the project's lib folder and try to add a folder, instead of being able to add a "directory", it gives me the option to add a "package". Here is a screenshot of what it looks like:
However, in my new projects, the menu looks different. It says "directory" instead of "package" as shown here:
I don't know if whatever is different about my projects that is causing one to say "package" and the other to say "directory" is the reason that the project with "package" in the menu has access to Firebase Assistant, while the one with "directory" does not; however, I suspect that it might be.
I haven't been able to find anything that explains why one project would have "package" while another has "directory"; does anyone have an explanation? I would love to test out whether that difference is the reason Firebase Assistant isn't appearing.
You can try to run 'flutter clean', then re-sync the graddle.
I am assuming you are running android studio in administrator mode ? I had problems if I was not in administrator mode.
Sorry. I'm not good at english.
When I update my app to 1.1.0, firebase does not recognize new version.
In firebase, my app version is still 1.0.12 and does not receive any event.
iOS is working good. but only Google has a problem.
In Play Store, People can download 1.1.0 version.
What can I do?
in terminal do : flutter clean
I have a Xamarin.Forms project and I'm using the firebase messaging platform to provide push notifications to my app.
The last step that is stopping me from publishing the app is the lack of FirebaseInstanceId Nuget for xamarin.forms which seems to exist only for xamarin.android.
The reason behind why it is so important for my project is getting the cloud messaging token. From what I've seen throughout internet forums it wasn't covered clearly what to do in this situation.
The notifications in my app work in an unusual way. The user chooses one of around 30 options, and then depending on his choice he receives appropriate push notification.
So I've written a script that sends his choice to the firebase database and that is where his token is required so a javascript server connected to firebase could send him the push.
I hope I made it clear, and that that the solution wasn't covered previously on this forum. I'm still a beginner so a detailed solution or some suggestions would be really appreciated.
To implement notifications in Xamarin forms, you should do it on each platform(iOS and Android)and install Nuget packages to each platform.
Create a Xamarin.forms project name MyApp(Use this Name as an Example).
Right Click on the MyApp.Android(This is important, not MyApp) ---> Manage NuGet Packages
You should install these packages in Android Project:
(1). Xamarin.GooglePlayServices.Base
(2). Xamarin.Firebase.Messaging
Right Click on the MyApp.iOS(This is important, not MyApp) ---> Manage NuGet Packages
You should install these packages in iOS Project:
(1). Xamarin.Firebase.iOS.CloudMessaging
You can follow this article for more detail :firebase-cloud-messaging.
Since the tns-plugin-firebase update to version 15. When doing sidekick cloud builds I receive the message:
Unable to find a specification for Firebase/Core -> 5.5
I followed the intructions fron the community which basically tells to do pods repo update, I even rm -rf the .cocoapods folder and reinstall it.
When building locally it works, but when doing cloud builds with sidekick I received the abve mentioned message.
Is possibl that the pods repo update has to be done in the sidekick server too?, because if not I don´t have a clue why this is happening!!!
Thanks for ideas or hints.
Javier
The issue is indeed related to the Sidekick cloud build service. The pods management is done entirely on the cloud machines, even when you build from a macOS system.
Having said that, the pod is now updated to the latest available version and after a couple of hours (time needed to propagate the changes to the entire infrastructure), you should no longer experience the "Unable to find a specification for Firebase/Core -> 5.5" error while building for iOS in the cloud.
Please check if you can install this.
https://github.com/AjayMT/online-todos
I have an error with relase file meteor.
Please give me some step to install this app.
The last commit on that repo was 2 years ago, which is a lifetime in Meteor terms, so this is going to use a version of meteor which is way, way out of date. It would probably take a lot of work to get it to function with a supported version.
Whether you're looking for this as a way to learn Meteor or for something to actually use, you should be using the official todos app. The (correct) instructions for Meteor installation are here.