I know about [this question](https://stackoverflow.com/questions/37321728/firebaseinitprovider-firebaseapp-initialization-unsuccessful) but I don't think it helps me and the problem looks slightly different.

I'm doing this app where I need to implement AppsFlyer for tracking and I'm required to use only 2 components from Google Play Services:

> 
> com.google.android.gms:play-services-ads
> 
> 
> com.google.android.gms:play-services-gcm
> 
> 
> 

And I'm using the latest version of the Google Play Services, 9.0.2 that is.

The problem is that **on the first app launch after installing the app**, the app takes quite a bit of time to start. There's no log output and when the app starts doing something, the first line on the log is:

> 
> 06-16 16:50:23.782 22368-22368/com.company.app I/FirebaseInitProvider:
> FirebaseApp initialization unsuccessful
> 
> 
> 

I'm not using Firebase, how can I get rid of this? It really slows down the application initialization. Not a very good user experience...

**EDIT:**

I've added both libs, one at a time and I've realized that the GCM is the one causing the issue. When I add:

> 
> com.google.android.gms:play-services-gcm
> 
> 
> 

I start getting the "FirebaseApp initialization unsuccessful" log and the app takes a while to start. Perhaps downgrading "fixes" the problem, but that's not a very good solution.