Will importing a Google Project into Firebase interfere with or break the operation of any legacy applications using the related APIs? For example, we currently use the Youtube APIs to allow users to upload videos to a website. Would this be affected after migrating?
It shouldn't break the legacy applications since the API key etc will remain the same. I've migrated the Google Project to Firebase project. I used to use Google Cloud Messaging API. Now I migrated from GCM to FCM (Firebase Cloud Messaging) and the projectId, projectNumber or SenderID, API Key, all remained the same. I didn't have to change anything on the server side as well and it worked out of the box.
Also if you import your Google Cloud Project to Firebase Project, the project on Google Cloud Platform still remains and you can keep using the same API's for now in similar manner. It seems that only for GCM, Google App Invites and AdMob, you can 'choose' to upgrade to corresponding Firebase services.
Related
I have an old project which I still find useful that was originally built with Google Cloud Messaging, that I then had to convert to use Firebase Cloud Messaging. I haven't worked on it for years but find it useful for my friends to track my phone's position via a web page on my always-on Raspberry Pi.
I received an e-mail from Google Analytics which said
You are receiving this email because you own one or more Firebase
projects using Google Analytics. With the release of Google Analytics
4 properties, to keep using your Firebase projects with Google
Analytics, you must take action to accept the Google Analytics Terms
of Service for the following projects:
I tried following the upgrade instructions via the console and get a failure due to an internal error
To the best of my knowledge I don't use any of the analytics stuff, so my question is quite simple:
"Will my existing messaging to my phone from my web page still work?"
firebaser here
Sorry to hear about the problem you have when upgrading your project to GA4. Our team is aware of the problem, and working on a fix, so I recommend trying again in a few hours. Meanwhile check this page for status updates.
Firebase Cloud Messaging relies on Google Analytics data to build its dynamic audiences, which you can target when sending notification from the Firebase console. If you don't use dynamic audiences, you don't need Google Analytics to use Firebase Cloud Messaging.
We have implemented the google sign in our Android app using the GoogleSignIn client. The client ids were added to Google Cloud Platform, signing keys SHA-1 were added to the firebase console config, and we have downloaded google-services.json and included in the project. Everything works fine, app is released and has active users we don’t want to break.
Now because of some business reasons we need to integrate google sign in our app with a service that is already using another Google Cloud Platform project. We tried generating new keys Android OAuth keys but were blocked by the following quote:
The package name and fingerprint pair you provided is already used by an Android OAuth 2.0 client ID in this project or another project.
After removing the debug client ID in the old project we generated a new id in the new GCP project, but it fails on a client calls to google SDK and broke google sign-in on the clients using the older id.
On iOS generating key on the new project and swapping it with current one was enough to get it to work.
Can our app stay in the current GCP/firebase project and integrate with backend using another GCP project?
Is there a way to migrate current app to the backend GCP project without breaking currently released app (which is cooperating with a backend using the same GCP project)?
I'm working on a project where we have an Android tablet that cannot have google play services installed on it. Which features/services of firebase have a dependency on google play services to run?
Specifically I'm looking at real-time database, authentication, firestore, and firebase cloud messaging.
I spoke with a developer advocate that said that real-time database doesn't have that dependency, but I couldn't find any official documentation that states that.
firebaser here
Some Firebase products require Google Play Services, while others don't. Information on this is nowadays included in the Firebase documentation, so I recommend checking out dependencies of Firebase Android SDKs on Google Play services for the latest list.
You can see it from the documentation.
https://firebase.google.com/docs/android/android-play-services
I managed to run my app after migrating to non play services Firebase Auth, while the database and storage continue to work fine.
Google Pay service can basically installed apps in its sore onto the device, if you cannot use this you would need to make the app as a "progressive web app" instead then. https://developers.google.com/web/progressive-web-apps/
Effectively what you can do through a webpage, using firebase hosting/firebaseDB/storage you would want to simply install a npm i -g firebase-tools do a firebase init in your project folder and configure your firebase settings to use your apps distribution folder for AnglularCLI the public folder would be "dist"
with the old versioning, play-services-base and play-services-auth were required; eg. to use FirebaseAuth with a Google account. the documentation only states firebase-core (checked that yesterday, because of a similar dependency question). but most likely, the "Login with Google" auth-provider might not be available then - and you would have to offer alternate ways to register an account.
I would like to add Firebase Cloud Messaging to an existing Android app that is currently published on the Google Play Store.
However, when I log into the Firebase console and select 'IMPORT GOOGLE PROJECT' I don't see any projects come up. None of the Android apps I have on the Google Play Store show up.
Is an Android app not the same thing as a Google Project? Should I just create a new Firebase project?
TIA
Import Google Projects refers to importing existing Google Cloug projects
(from https://console.google.com).
This is important if you application is already using some Google Cloud API, like Google Cloud Messaging, and you now want to use Firebase.
If you don't are not already using a Google Cloud project, don't worry and simply create a new Firebase Project.
If you have existing Google Cloud projects, but they don't show up in the import menu, please contact Firebase Support.
I just saw two tutorials one with Google Play Services to login and then use achievements, ladder, etc. So it has compile 'com.google.android.gms:play-services-plus:8.4.0' to login.
And in Firebase tutorial we use 'compile 'com.google.firebase:firebase-auth:9.0.0'
Isn't that similar services to connect and we can't use both in one?
It would be big gap in UI/UX if user would connect two times to similar service.
Question:
Could I use one auth for both?
You should understand that firebase was once an independent organisation and but later on acquired by google. The earlier document were found at Firebase Previous Docs but now its part of google and google and accessed here Firebase Google Current Docs. So even before acquiring firebase google services were there stuffs like GCM google cloud messaging which is now firebase cloud messaging. So it turns out that after for authentication using firebase can be from various accounts like google,facebook,twitter,github etc but in that example of yours you have an option of logging in as google account only because is a google plus. So consider to stay updated, firebase is simple and current while the other will be completely deprecated later.