The Firebase Blog

Email Verification in Firebase Auth

February 21, 2017

Laurence Moroney
Developer Advocate

Posted by Laurence Moroney - Staff Developer Advocate Email Verification

Exploring Email Verification

https://github.com/firebase/quickstart-android

This email is shown on the Email Templates tab in the Authentication section of the Firebase console. From here you can edit the action link, or the reply address so that it appears to be from your domain, instead of authui-xxxx.firebaseapp.com as shown above.

Here you can see what happens once the account is verified and I sign in again.

You'll also see that this identity is present as a user in the Firebase console. You can manage them from there -- including changing their password or removing them from your app altogether.

Coding for Email Verification

Details on coding for email verification can be found in the Manage Users section of the Firebase documentation (Android, iOS, Web). For the rest of this post, I'll be looking at the Android code, but the implementation on the other platforms is very similar.

The core functionality is found on the FirebaseUser object. On it is a sendEmailVerification() method, which returns as Task used to asynchronously send the email, and report on the status. If the task is successful, you know the email was sent. Here's an example:

final FirebaseUser user = mAuth.getCurrentUser();
        user.sendEmailVerification()
                .addOnCompleteListener(this, new OnCompleteListener() {
                    @Override
                    public void onComplete(@NonNull Task task) {
                        // Re-enable button
                        findViewById(R.id.verify_email_button).setEnabled(true);

                        if (task.isSuccessful()) {
                            Toast.makeText(EmailPasswordActivity.this,
                                    "Verification email sent to " + user.getEmail(),
                                    Toast.LENGTH_SHORT).show();
                        } else {
                            Log.e(TAG, "sendEmailVerification", task.getException());
                            Toast.makeText(EmailPasswordActivity.this,
                                    "Failed to send verification email.",
                                    Toast.LENGTH_SHORT).show();
                        }
                    }
                });

In this case, the user is retrieved from mAuth.getCurrentUser(), and the sendEmailVerification() method is called on it. This gets Firebase to send the mail -- and if the task was successful, you'll see that a toast will pop up showing that it happened.
After the user clicks the link in the email, subsequent calls to user.isEmailVerified() will return true. Here's how it is used in the sample app:

mStatusTextView.setText(getString(R.string.emailpassword_status_fmt,
                    user.getEmail(), user.isEmailVerified()));

Do note that the FirebaseUser object is cached within an app session, so if you want to check on the verification state of a user, it's a good idea to call .getCurrentUser().reload() for an update.

In the sample app it just shows on the activity if the user's email address is verified or not. For your app you could limit functionality based on this state -- even to the extent of denying them access to the signed in section of the app.

You can learn more about Firebase Auth, including sign-in with other providers such as Google, Facebook, Twitter and more on the Firebase developers site.

Top sessions for mobile developers at Google Cloud Next 17

February 17, 2017

James Tamplin
Product Manager

Posted by James Tamplin, Product Manager, Firebase

Google Cloud Next 17 is three weeks away! It's a great event for anyone looking for insight on Firebase and mobile development. Scanning through the session catalog, here's a sampling of the must-see sessions that mobile developers should attend.

If you're a mobile development rookie, your first stop should be "What to consider when developing mobile apps," in which Laurence Moroney, Google staff developer advocate, surfaces some of the gotchas of developing for mobile devices such as poor connectivity and offline devices, access control and battery life.

Then, march on over to "Zero to App: Live coding an app with Firebase and GCP," which will be a very cool live demo. Watch in awe as Googlers Mike McDonald, Jen Tong and Frank van Puffelen do simultaneous live coding of an app across both iOS and Android. You'll leave with an appreciation of how easy it is to code with Firebase, and how easy it is to scale with GCP.

For mobile devs that just want to focus on delivering a great UX, "serverless" development helps remove a big set of concerns from their plate. If that describes you, go see "Google Cloud Functions and Firebase," with Firebase team members Thomas Bouldin, software engineer and Brendan Lim, product manager, who will show you how to extend Firebase backend services with Google Cloud Functions to make the next generation of mobile and web apps.

Once you've built that awesome mobile app, you'll want analytics to understand how people use it. But building analytics infrastructure can be painful, and the same goes for log ingestion pipelines, and managing a data warehouse. We've got you covered. In "Gaining deeper insights from Firebase Analytics with Google BigQuery," Google developer advocates Todd Kerpelman and Arun Venkatesan will show you how to use Firebase Analytics and augment it with BigQuery and data visualization tools like Data Studio.

Of course, that's just the tip of the iceberg. For the full story, check out the schedule for a full listing of the keynotes, bootcamps and over 200 breakout sessions. Hope to see you there!

"How do I add Firebase Analytics to an app that's already using Google Analytics?"

February 16, 2017

Todd Kerpelman
Developer Advocate

Remote Config targeting First, Let's Talk Eventsfunc recordGameOver() { let tracker = GAI.sharedInstance().defaultTracker let gameOverEvent = GAIDictionaryBuilder.createEvent(withCategory: "gameOver", action: "totalScore", label: "", value: myGameStats.totalScore as NSNumber) let enemiesBeatenEvent = GAIDictionaryBuilder.createEvent(withCategory: "gameOver", action: "enemiesBeaten", label: "", value: myGameStats.enemiesBeaten as NSNumber) let roundsSurvivedEvent = GAIDictionaryBuilder.createEvent(withCategory: "gameOver", action: "roundsSurvived", label: "", value: myGameStats.roundsSurvived as NSNumber) tracker?.send(gameOverEvent.build() as [NSObject: AnyObject]) tracker?.send(enemiesBeatenEvent.build() as [NSObject: AnyObject]) tracker?.send(roundsSurvivedEvent.build() as [NSObject: AnyObject]) } FIRAnalytics.logEvent(withName: "gameOverTotalScore", parameters: [kFIRParameterValue: myGameStats.totalScore as NSObject]) FIRAnalytics.logEvent(withName: "gameOverEnemiesBeaten", parameters: [kFIRParameterValue: myGameStats.totalScore as NSObject]) FIRAnalytics.logEvent(withName: "gameOverTotalScore", parameters: [kFIRParameterValue: myGameStats.totalScore as NSObject]) let finalStats = ["totalScore": myGameStats.totalScore as NSObject, "enemiesBeaten": myGameStats.enemiesBeaten as NSObject, "roundsSurvived": myGameStats.roundsSurvived as NSObject] FIRAnalytics.logEvent(withName: "gameOver", parameters: finalStats) whole video Adding Firebase the Correct WayGoogleService-info.plistGoogleService-info.plistGoogleService-info

What you'll get back will be a superset of the plist file you'd get from both Firebase Analytics and Google Analytics -- if you examine its contents, you should see a TRACKING_ID entry equal to your Google Analytics tracking ID, along will a whole bunch of new Firebase info. Replace your old GoogleService-info file with this new one, go through the rest of the Firebase installation process, and you're ready to go. Option 1: Just Use Two Analytics SDKsfunc recordGameOver() { // All the old code you had previously to record Google Analytics // … // … So much code … // … // Now add the Firebase stuff let finalStats = ["totalScore": myGameStats.totalScore as NSObject, "enemiesBeaten": myGameStats.enemiesBeaten as NSObject, "roundsSurvived": myGameStats.roundsSurvived as NSObject] FIRAnalytics.logEvent(withName: "gameOver", parameters: finalStats) }

But this solution has a few drawbacks. For starters, you're now sending down data to two different analytics packages, which generally means that your client is making more network calls then before, and that means your app is using more of your user's mobile data and negatively impacting their battery life. On the other hand, Firebase Analytics tends to be quite conservative when it comes to making network calls, so we're only looking at a minor bump on top of your Google Analytics traffic. Option 2: Use Google Tag Manager to Report Events Everywhere

The nice part about this solution is that you only need one set of analytics-reporting code on your client. In our example, we would have a much simpler implementation where we could completely eliminate the Google Analytics calls:func recordGameOver() { let finalStats = ["totalScore": myGameStats.totalScore as NSObject, "enemiesBeaten": myGameStats.enemiesBeaten as NSObject, "roundsSurvived": myGameStats.roundsSurvived as NSObject] FIRAnalytics.logEvent(withName: "gameOver", parameters: finalStats) // That's it! }

Next, you'll create a trigger for each Firebase Analytics events you want to correspond to. In our case, we'd want to create a trigger that fires whenever we see an event name called "gameOver"

Finally, you'll create tags where you respond to these triggers by sending off events to Google Analytics (referred to as Universal Analytics within Google Tag Manager). You can also send off events to services such as AppsFlyer, Kochava, Tune, and others.

Now I like this approach because, frankly, any opportunity you get to write less code is usually a good thing. This also gives you the flexibility to report some events to Google Analytics but not others, (if you wanted to start reporting some events exclusively to Firebase Analytics), or change how you're reporting your Firebase Analytics events to Google Analytics, even after the app has shipped!

Option 3: Use BigQuery to Merge Everything

Now, granted, this solution only really makes sense if you're already a Google Analytics 360 customer and are currently using BigQuery to drive most of your custom reports. If this sounds like you, then updating your BigQuery queries to grab data from both data sources may be a reasonable option.

SELECT AVG(hit.eventInfo.eventValue) FROM `my_awesome_app.ga_sessions_20170123`, UNNEST(hits) AS hit WHERE hit.eventInfo.eventCategory = "gameOver" AND hit.eventInfo.eventAction = "totalScore" func recordGameOver() { let finalStats = ["totalScore": myGameStats.totalScore as NSObject, "enemiesBeaten": myGameStats.enemiesBeaten as NSObject, "roundsSurvived": myGameStats.roundsSurvived as NSObject] FIRAnalytics.logEvent(withName: "gameOver", parameters: finalStats) // That's it! } SELECT COUNT(*), AVG(total_score) AS average FROM ( SELECT event_param.value.int_value AS total_score FROM `firebase-project.com_example_awesome_app.app_events_20170123`, UNNEST(event_dim) AS event, UNNEST(event.params) AS event_param WHERE event.name = "gameOver" AND event_param.key = "totalScore" UNION ALL SELECT hit.eventInfo.eventValue AS total_score FROM `my_awesome_app.ga_sessions_20170123`, UNNEST(hits) AS hit WHERE hit.eventInfo.eventCategory = "gameOver" AND hit.eventInfo.eventAction = "totalScore" ) Google Cloud Big Data Blog

So there ya go, folks; a few pointers on how to add Firebase Analytics to your app that's already set up for Google Analytics. (Or, for that manner, any other analytics platform.) Once you've gotten that set up, I recommend trying out some Firebase features that make use of Firebase Analytics data: deliver a new Remote Config setup to users with a specific user property, or send a Notification to a Firebase Analytics Audience that you've created. And feel free to start tracking more Firebase Analytics events -- remember, it's free and unlimited, no matter how many users your app might have. There's a lot more exciting tools and features coming out for Firebase Analytics over the next year, so it's never too early to start adding Firebase Analytics to your mobile app. Give it a try!

Complex Sign-in user flows made easy on Android with Firebase

February 9, 2017

Laurence Moroney
Developer Advocate

Firebase Auth

Getting Started

The best way to get started is to go to GitHub and use FirebaseUI!

here

Before you can run it, you'll need a Firebase project in the Firebase console, which in turn will give you a google-services.json configuration file. To get this, follow these steps:

Running the FirebaseUI Auth App

You're now ready to run the app. On some versions of Android Studio, you might get an error telling you that Instant Run isn't working. If that's the case, you can disable it on the Android Studio->Preferences->Instant Run menu.

Android's hint selectorIf you aren't signed into Google or any other accounts on the device, you won't see this, and will get taken to the Sign-in Screen instead.

If there's no Google Account, but you sign in with Google, you should have the option to create a new one, or use an existing one

If there is only one Google Account, and you used it previously to sign in, then you can sign in right away with it.

If there are multiple Google Accounts, you should be given the option to choose one, add an existing one, or create a new one.

Exploring the Code

To explore the code, go back to Android Studio, and look in the App folder. In it, you'll see an 'auth' folder, and within that there are three activities.

FirebaseAuth auth = FirebaseAuth.getInstance(); if (auth.getCurrentUser() != null) { startActivity(SignedInActivity.createIntent(this, null)); finish(); }R.id.sign_in@OnClick(R.id.sign_in) public void signIn(View view) { startActivityForResult( AuthUI.getInstance().createSignInIntentBuilder() .setTheme(getSelectedTheme()) .setLogo(getSelectedLogo()) .setProviders(getSelectedProviders()) .setTosUrl(getSelectedTosUrl()) .setIsSmartLockEnabled(mEnableSmartLock.isChecked()) .build(), RC_SIGN_IN); } @Override protected void onActivityResult(int requestCode, int resultCode, Intent data) { super.onActivityResult(requestCode, resultCode, data); if (requestCode == RC_SIGN_IN) { handleSignInResponse(resultCode, data); return; } showSnackbar(R.string.unknown_response); } private void handleSignInResponse(int resultCode, Intent data) { IdpResponse response = IdpResponse.fromResultIntent(data); // Successfully signed in if (resultCode == ResultCodes.OK) { startActivity(SignedInActivity.createIntent(this, response)); finish(); return; } else { // handle failure conditions } } <style name="DarkTheme" parent="FirebaseUI"> <item name="colorPrimary">@color/material_gray_900</item> <item name="colorPrimaryDark">@android:color/black</item> … </style> </p> <p> <item name="colorPrimary">@color/material_gray_900</item> </p> <p> <item name="colorPrimaryDark">@android:color/black</item> </p> <p> … </p> <p> @OnClick(R.id.sign_in) public void signIn(View view) { startActivityForResult( AuthUI.getInstance().createSignInIntentBuilder() .setTheme(R.style.DarkTheme) .setLogo(getSelectedLogo())
iOSJavascripthttps://github.com/firebase/FirebaseUI-Android

Firebase Analytics Quick Tip: The 'value' Parameter

February 7, 2017

Todd Kerpelman
Developer Advocate

FIRAnalytics.logEvent(withName: "workout_complete", parameters: [ "time": 1804 "exercise_type": "interval" "intensity": 2 ])


FIRAnalytics.logEvent(withName: "workout_complete", parameters: [
    "time": 1804
    "exercise_type": "interval"
    "intensity": 2
    kFIRParameterValue: 1804
  ])

workout_complete

Of course, the value parameter won't always give you all the information you need. If you were interested in comparing the average workout time for your interval workouts to the average workout time for your yoga workouts, you'd still need to use BigQuery to get that kind of data analysis. But I think you'll find you can get a surprising amount done just with the value parameter.workout_completeinvite_friendseat_mealour docs