Is Google Play Services for Froyo compatible with Android 2.3 and higher?

Question

When reading the documentation on google play settings , it looks like google play services for Froyo Rev. 12 should be compatible with Outlook with Android 2.3 and higher.

However, I am having problems with this in my GPSTest app on Github , which currently includes Google Play services for Froyo.

If I try to create a project using Google Play Services for Froyo Rev. 12 with an element:

<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" /> 

... is included in AndroidManifest.xml, I get a build error:

 Error: No resource found that matches the given name (at 'value' with value '@integer/google_play_services_version'). 

It is expected (from my current understanding) because this integer does not exist in the Google Play Services for Froyo project (sdk \ extras \ google \ google_play_services_froyo \ res \).

If I remove this element from the manifest, it works great when creating and debugging an application through Eclipse (as you would expect). However, when I export the APK, install on the device (Samsung Galaxy S3 Android 4.3, Google Play Services v4.0.34 - by downloading the exported APK from Dropbox), and run it, I get the following error on startup and the application crashes:

 java.lang.IllegalStateException: The meta-data tag in your app AndroidManifest.xml does not have the right value. Expected 4030500 but found 0. 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" /> at com.google.android.gms.common.ba(Unknown Source) at com.google.android.gms.maps.a.bn.a(Unknown Source) at com.google.android.gms.maps.mg(Unknown Source) at com.google.android.gms.maps.ma(Unknown Source) at com.google.android.gms.aba(Unknown Source) at com.google.android.gms.aba(Unknown Source) at com.google.android.gms.maps.SupportMapFragment.onCreate(Unknown Source) at android.support.v4.app.Fragment.performCreate(Unknown Source) at android.support.v4.app.FragmentManagerImpl.moveToState(Unknown Source) at android.support.v4.app.FragmentManagerImpl.moveToState(Unknown Source) at android.support.v4.app.BackStackRecord.run(Unknown Source) at android.support.v4.app.FragmentManagerImpl.execPendingActions(Unknown Source) at android.support.v4.app.FragmentManagerImpl.executePendingTransactions(Unknown Source) at android.support.v4.app.FragmentStatePagerAdapter.finishUpdate(Unknown Source) at android.support.v4.view.ViewPager.populate(Unknown Source) at android.support.v4.view.ViewPager.populate(Unknown Source) at android.support.v4.view.ViewPager.onMeasure(Unknown Source) at android.view.View.measure(View.java:16848) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5245) at android.widget.FrameLayout.onMeasure(FrameLayout.java:310) at android.view.View.measure(View.java:16848) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5245) at com.android.internal.widget.ActionBarOverlayLayout.onMeasure(ActionBarOverlayLayout.java:302) at android.view.View.measure(View.java:16848) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5245) at android.widget.FrameLayout.onMeasure(FrameLayout.java:310) at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2586) at android.view.View.measure(View.java:16848) at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:2189) at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1352) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1535) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1249) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6364) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:791) at android.view.Choreographer.doCallbacks(Choreographer.java:591) at android.view.Choreographer.doFrame(Choreographer.java:561) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:777) at android.os.Handler.handleCallback(Handler.java:730) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:5455) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1187) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) at dalvik.system.NativeStart.main(Native Method) 

I use Google Play services for Froyo Rev. 12, and here is AndroidManifest.xml with the full version:

 <manifest android:versionName="3.2.65 (834000-30)" android:versionCode="3265130" package="com.google.android.gms" xmlns:android="http://schemas.android.com/apk/res/android"> <uses-sdk android:minSdkVersion="8"/> </manifest> 

Is there a way to deploy one APK on Google Play using Google Play Services for Froyo Rev. 12 for Android 2.2 and higher?

Or do I need to deploy two APKs on Google Play (one of which uses Google Play Services for Froyo for Android 2.2, and the other uses Google Play Services for Android 2.3 and higher) if I want to keep supporting Froyo?

Has anyone successfully deployed Google Play Services for Froyo on Android 2.3 and up?

Answer 1

Yes, Google Play Services for Froyo is shipped from Android 2.3 and up, and the manifest element is not needed.

It seems that this problem was actually a bug in the Google Maps application.

An update to the Google Maps app started rolling out yesterday (12/12/2013), and my phone installed it today (new version v7.5.0). After that, the startup failure problem magically disappeared. I even came back and tested the old version of the APK from Dropbox, which, of course, was crashing (just in case my other changes in Eclipse fixed something), and now it works.

(Note that you must use Google Play Services for Froyo if you support API level 8 - Android 2.2. If your minSdkVersion is> = 9, you must use the latest version of Google Play Services since new features are not added to the services Google Play for Froyo.)

Answer 2

You do not need

 <meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" /> 

This applies to the updated version of Google Play Services. If you use the Google Play Services for Froyo library, you don’t need it.

Now let's talk about another problem. How exactly do you "debug an application through Eclipse"? Are you using a debug key or release a key? How do you install the APK inside the device? did you try to uninstall → install? Did you use the ADB installation or did you download the APK as an Alpha / Beta test? Are you sure you are installing the correct APK?

Answer 3

This is a strange error, I solved this problem this way - just changed android: value = "@ integer / google_play_services_version" to 3265130.

Answer 4

Creating an integer resource seems to solve the problem.

But in the end I ran into each other.

There is no package " ads.AdActivity ". Even adding a version of froyo:

compile 'com.google.android.gms:play-services:3.2.65'

The documentation says nothing about the froyo version:

https://developers.google.com/mobile-ads-sdk/docs/

Answer 5

For me, java.lang.IllegalStateException seems to have occurred due to the fact that I had previously contacted all Google Play services (version 22) before moving to Google Play services for Froyo. There must have been some remainder of version 22 in the assembly, and a full cleanup and recovery fixed the problem.