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

3,397 views
Skip to first unread message

Sadart Abukari

unread,
Sep 24, 2015, 6:17:59 PM9/24/15
to CodenameOne Discussions
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" /> is required in Manifest.
I know the following: Adding
android.xapplication=\<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />\<activity android:name="com.google.android.gms.ads.AdActivity" android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize" />
will produce failed build.

When I add only this
android.includeGPlayServices=true
I see no gms defined in Manifest file

Shai Almog

unread,
Sep 25, 2015, 12:22:08 AM9/25/15
to CodenameOne Discussions
That entry is already included by android.includeGPlayServices=true and is redundant.

Sadart Abukari

unread,
Sep 25, 2015, 1:19:19 AM9/25/15
to CodenameOne Discussions
Does it mean the AndroidManifest.xml file will contain that entry when I search or that entry is hidden. I am doing Airpush Native Implementation and have
android.includeGPlayServices= true defined yet I can't see the
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />
definition in the AndroidManifest.xml file from the build. The AndroidManifest.xml file is attached.


The Airpush guys replied in an email. Excerpt below

Add below line exactly in his Manifest file. Also, it appears you are using an old Google Play Services lib and need to use the updated one. These should resolve your issue! Let me know if you still have troubles.

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

Chen Fishbein

unread,
Sep 25, 2015, 9:00:39 AM9/25/15
to CodenameOne Discussions
Hi,
The manifest you attached cannot be open, but if you added the android.includeGPlayServices= true correctly that meta data line should have been added to your manifest, if it's not there that property wasn't added properly.
How did you added that? using the build hints tab or directly to the properties? I assume directly to the properties.(if you open the properties manually it should look like this: "codename1.arg.android.includeGPlayServices=true")

Sadart Abukari

unread,
Sep 25, 2015, 3:26:28 PM9/25/15
to CodenameOne Discussions
Thanks. My first time seeing the properties files. Checked in it and saw android.includeGPlayServices \ = true. I then went into the properties and realized there is a space after android.includeGPlayServices. Remove the space and now the play meta shows in manifest.
One thing to note is that I have never seen any manifest from any of my codenameone builds which can be opened directly in the browser. I always open them up with text editors.

Shai Almog

unread,
Sep 26, 2015, 12:24:57 AM9/26/15
to CodenameOne Discussions
You can use include sources to see the manifest XML.
Reply all
Reply to author
Forward
0 new messages