In the new version of the Google Play Services library there is a lot of new code for the material design which really made my app huge and it crossed the border of 65 536 methods.
So I found a solution to the problem in stackoverflow. I will paste it here:
I realise that this is an old question, but I had the same problem today (for real devices not for the emulator) and have found a solution.
I know that you can add code to prompt the user to upgrade to the latest version (see the comment by @nathan-walters) but, for complicated reasons, in my case I need to work with whatever version the user already has installed on their device (if any) and hence prefer to compile/build with an older version of the client library (google-play-services_lib)
So researching further, I unpacked the xml that Android SDK Manager uses to find and install the ‘extras’ packages including the latest version of Google Play Services.
If you are interested start here: https://dl-ssl.google.com/android/repository/addon.xml
For the current version (as of Nov 10th 2014) that gives you the library for google-play-services_lib at:
The older versions are in the same location on the google servers (although they could disappear at any time), so if you are prepared to move the current installed library aside and manually unpack an older zip then you can install an old version. I found the following:
The same technique would allow you to test against the non-upgradable older versions Google Maps (Google Play Services) hardwired in older versions of the emulator. I haven’t tested all these versions against the emulator but have successfully tested Google Maps in the emulator for an AVD based on Google APIs (API 19).
Google does make the occasional attempt to bring the emulator up to date. Here is an issue tracker thread discussing version incompatibility issues between the client library and the emulator and google’s various attempts to fix them: https://code.google.com/p/android/issues/detail?id=57880