An earlier Firebase registration flow for Flutter

Registering an application with Firebase associates a platform identifier with project configuration. It is distinct from initializing Firebase in the Dart application and enabling a particular service.

The earlier iOS registration

The source created a Firebase project, registered the iOS bundle ID, downloaded GoogleService-Info.plist, and added it to the Runner project through Runner.xcworkspace. File presence and target membership both matter. No original configuration file is imported here.

The earlier Android registration

The source registered the Android package, placed google-services.json under android/app, and changed these Gradle settings:

buildscript {
    ext.kotlin_version = '1.3.50'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath 'com.google.gms:google-services:4.3.3'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

apply plugin: 'com.google.gms.google-services'

Those versions belong to the earlier toolchain. Registering the wrong package or bundle ID is not repaired by merely copying a configuration file.

The Firebase Flutter setup guide describes the current supported setup. No Firebase project, account, or application registration was created for this revision.

← Back to the garden