20 August 2013
Comments: 0

Unity: Creating an Android library when Eclipse hates you

OK, so Prime31 got back to me about the bug report.

To paraphrase: “Not our problem”.

Now how did I know that they were going to say that? Thanks for the help guys.

Unfortunately, if AdMob are anything like the other Google departments that I’ve had experience with, the best I can hope for is a canned response from a robot.

The only way I’m going to prove whether whether it’s Prime31′s plugin or AdMob, is by writing a replacement for Prime31′s plugin.

First step: use Eclipse to create a new Android project.

First problem: Eclipse fails to create a new Android project.

Nice one Google! The Android bundle which includes Eclipse won’t create an Android project. All the options are there, it’s just that clicking the “Finish” button does nothing except spit out a broken project missing all of the Android specific stuff.

I’m not the only one experiencing the problem.

To get past this step, I had to resort to creating a project from the command line.

  1. Change into the sdk folder and create a work folder called project:
    mkdir project
  2. Lookup the id of the target to use
    ./tools/android list targets
  3. Create the Eclipse project from the command line
    ./tools/android create project –target 6 –name adlib –path project/adlib –package org.burlock.adlib –activity adlib
  4. Finally, open Eclipse, create a new Android project from Existing code, and select the project folder

So much time has been wasted, first with MoPub not working at all, then with Prime31/AdMob not working on an Amazon device, despite plenty of evidence that AdMob should work without issue.