Conflits with firebase_core:App craches on first open when I add onesignal package to pubspec.yaml

[abd3llatif]

To reproduce error :
flutter create
add onesignal: ^1.1.0 to pubspec.yaml
add firebase_core: too
flutter run

** Note: data should be cleared -> the error appear in the first open of the apk.

Error: Error connecting to the service protocol: HttpException: Connection closed before full header was received, uri = http://127.0.0.1:50309/V

[rgomezp]

Could you please provide more info by following our issue template? Thanks

[abd3llatif]

The version used of OneSignal flutter sdk is ^1.1.0, it s used with firebase_core version 0.4.0+1 last version of firebase core sdk for flutter.

[abd3llatif]

Gradle App module :

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 28

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.example.testonesignal"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'


}

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

Gradle Project level:

buildscript {
    repositories {
        google()
        jcenter()

    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.3.0'
        classpath 'com.google.gms:google-services:4.2.0'
    }
}

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

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Pubspec.yaml

name: testonesignal
description: A new Flutter project.

version: 1.0.0+1

environment:
  sdk: ">=2.1.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^0.1.2
  onesignal: ^1.1.0
  firebase_core:

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:

  uses-material-design: true

[rgomezp]

@AbdoXLabs I don't see how the OneSignal plugin is causing this issue. The error
Error: Error connecting to the service protocol: HttpException: Connection closed before full header was received, uri = http://127.0.0.1:50309/V doesn't mention anything with OneSignal

[abd3llatif]

Yeah sure, the log is not clear ! just try to reproduce the error by creating a flutter project and add onesignal: ^1.1.0 and firebase_core: to your pubspec.yaml.
then run the app on android.

[rgomezp]

Thank you for your patience. We will be releasing an update soon that we hope fixes several issues. In the meantime, can you try following this?

[rgomezp]

This has since been fixed @AbdoXLabs