Following a recent update to the version of Google Play Services Library in my workspace, I can't for the life of me get the GPSL jar to export in my apk file. I have followed smug's guide - successfully getting the magic green tick in the Android / Library tab. I've tried so many different ways, adding the .jar file to libs, referenced libraries, android private libraries, android dependencies etc and ticked/unticked the Order and Export tab. I've now tried so many variations that I'm lost as to where I should be. Firstly, do I need GPSL at all? The app does not use maps, log-ins or leaderboards etc. All I use Google Play for is to distribute my app and I look at the distribution stats. If I do need it, can someone look at their succesfully included GPSL.jar and let me know where it needs to be. Help - it's my birthday! I shouldn't be doing this on my birthday.

It is a library so it only needs to be imported by: 1. Right clicking your project and click Properties at the bottom 2. In the tab options click Android 3. At the bottom you will see is Library. Click add and find the Google Play Services Library. It should be listed. If it is not listed, you've probably added the Google Play Services Library improperly. If you've done the above your project should compile with no issues.

Hi mysps It is listed with the magic green tick!

Yes it has a green check mark with the location of the google play services file. Don't click the button: Is Library ..

The 'Is library' is not ticked

no, its not ticked.

It's annoying to be sure. 1) Make sure you have the absolute latest Google Play services. In eclipse, menu your way to "Window" -> "Android SDK Manager". Make sure you have v15, the latest. 2) Once updated, "remove" whatever google play services you have in your workspace. 3) Install Google Play services in accordance with my manual. Make sure 'is library' is not ticked. Make sure you remove 'google-play-services-remove.jar' if it's there. 4) Cross your fingers, 'clean' your project, rebuild, give it a go. Cheers! -- Smug Edit: Don't choose 'Google Play Services for Froyo'. That's something new, and will not be supported in any buzztouch project. Too little too late, lol!

Hi Smug /all I have done the above, but decided to re-do for my own peace of mind. But still no joy. Here are a couple of screenshots - can you spot anything? https://www.dropbox.com/s/cilck4eas14t581/Google%20Play%20Services%20Library%20Screenshots.pdf

You shouldn't reference the 'Google API' the way we did in BTv2… We use 'Android' API v14… Part of why we need GPS now, and did not then… Switch from 'Google API' to 'Android API' and see if that helps... Cheers! -- Smug

Morning smug. I think my app is version 2. It was created in July (ish) 2013. I shall try regardless.

I switched to Android API 17 (as I have it installed) but this has given a couple of red errors as follows: GeoPoint cannot be resolved to a type The import com.google.android.maps cannot be resolved Shall I install 14 and try that?

It's 'supposed' to be API 14… Android 4… Give that a go and see if anything changes… Cheers! -- Smug

API 14, Android 4.0 installed and used. Unfortunately, still no GPSL.jar in apk file. https://www.dropbox.com/s/shch2nthdgw1h5h/Google%20Play%20Services%20Library%20Screenshots2.pdf

Have you thought about downloading a new project and trying with that? I'm not sure 'why' things aren't working…. but it really shouldn't be that hard. Something I can't think of must be at play, but of course I'm coming up blank as to why. Let us know what comes of this; I can only hope it's some small detail that's being missed. Cheers! -- Smug

I'll download a new project and see how that goes. I was hoping to avoid this as I have made so many post-download alterations, but I guess it is last resort time. You're right it shouldn't be this hard and there was no problem when I integrated an older version of GPSL using your guide previously. I'll keep you posted and, as always, your help is most appreciated.

I've gone out on a bit of a limb here Smug - My app has 13% current users on Android 2 and 3. So if I update my app to BTv3 then I would lose these people. By definition, my app is targeted at those who have not updated their music taste in 30 years, so some are unlikely to update their mobile devices regularly. I've tested the beta version of my app without GPSL (which is BTv1.9 or 2 I believe) and is working fine on my device so I've published to production. I'll see how it goes without GPSL included. If it fails for some reason then time to download a new project and say goodbye to those on Android 2 & 3.

Well, you'll only use google play services in BTv3 projects… if it's still a BTv2 project you won't need it. And if your BTv3 project doesn't use google resources (maps, analytics, anything that requires some kind of Google API key) then heck, leave it out. No one cares anyway. But if this is the case, you'll 'want' to keep the 'google-play-services-remove.jar' because it's sort of a 'placeholder' for google specific routines. The new projects need one or the other, just not both at the same time. Cheers! -- Smug

'No one cares anyway' - never a truer word spoken. You really should be asleep. Get to bed.