This Worked for me. Thanks for the help. 
I had same problems since July 18th and removing [“plugin.google.play.services”] worked for me too. Thank you Ingemar_corona.
Is this something that can be fixed at Corona’s end, or are the different versions of the Google Play lib embedded within the AdMob/Google Analytics libs making this impossible to fix?
Can a note at least be added to the Google Analytic plugin docs for now saying that you cannot use AdMob at the same time?
I’ve just spent time trying to add GA to a client’s app only to find it doesn’t work on Android due to this Google Play issue. These things happen, but would be good if it could have been avoided.
In my opinion, AdMob IS NOT the problem, I re-built the app
- without plugin.google.play.services
- with AdMob enabled
and it’s OK…
I cannot be 100% sure because I don’t use AdMob in the app, but since march, I use a build.settings with
[“CoronaProvider.ads.admob”] =
{
– required
publisherId = “com.coronalabs”,
},
and had no problem until July the 18th.
After reading different suggestions in this thread, I tried to disable AdMob without success.
Finally I tried ingemar_corona’s solution (disable plugin.google.play.services) and it worked fine.
Then I re-enabled AdMob lines and it’s still working.
Also note that the build’s size came back to it’s original size when disabling plugin.google.play.services
A good test would be to check the Corona GA sample with and without plugin.google.play.services
I’ve just tried taking out the plugin.google.play.services, but I get this error:
java.lang.IllegalStateException: The meta-data tag in your app's AndroidManifest.xml does not have the right value. Expected 8487000 but found 4242000. You must have the following declaration within the \<application\> element: \<meta-data android:name="com.google.android.gms.version" android:value="@integer/google\_play\_services\_version" /\>
Since this is an SDK build rather than Enterprise I’m not setting the manifest fields manually, so I guess this is being set by either Corona or one of the plugins.
Has anyone else had the same error?
This plugin: “CoronaProvider.ads.admob”.
should not be used any more. Google is killing it in a month or so. We’ve not had it up for new people to use in some time.
AdMob V2 “plugin.google.play.services” is our current version of AdMob. It however uses an incompatible version of the Google Play Services to what Google Analytics needs. We are working to solve this on multiple fronts, but it’s a huge project with many moving pieces.
We understand this is a big issue and we are working on addressing it as fast as we can. We still have a lot to do.
Rob
Just so I’m sure I understand, that means that anyone who requires “plugin.google.play.services” for anything at all cannot use Google Analytics at the moment, correct?
Not necessarily. Many plugins work with both versions of the GPS plugin. As far as I know GA is the only one having an issue. It’s the only one that’s popping up.
Rob
In other words, it is not possible to use AdMob and GoogleAnalytics together by now, right?
Do you have any plans to adjust this problem?
I have a big multiplatform project to be released this week!
Anyway, thanks for the support. I use Corona to almost 3 years and have always been satisfied!
https://bitbucket.org/Jonjonsson/google-analytics-for-corona-sdk/
I use this in my app works fine. This rest api is easy to use and is cross platform on apple tv, mac, android, windows, windows phone, kindle, kindle tv fire tv, iOS, and android tv.
We’re experiencing the crash as well…
So basically, we have to choose between Google Analytics and AdMob?
There is no other way to make it work? We really need them both…
I want to add that I have been using Jon Johnsons module with no problems since its inception.
Rest API it is then!
I just had the same problem. I removed Google Analytics and I am back to using Flurry. In any case it sounds like progress to me. Version 8x is a much newer version than 4x. So sooner or later to resolve this we might get the newer version.
Any news about the fix people?
I can’t provide a date on when this will be fixed. If you need to release now or soon, you should find an alternative like Flurry. It’s a complex issue with multiple dependencies that have to be met first.
Oh ok, no problem 
Thanks so much and good luck with the issue, i know you guys can fix it, good team