Fixed a *strange* problem

Ok, we're getting there. MobFox has approved my apps; they are uploaded to the Android Marketplace. However, in the two apps I've tried - levels 4 and 5 - two problems have appeared. At level four, there are is no MobFox add window showing up; and at level 5, there is a crash, with a mobfox class not found exception.

The first thing to do is figure out how to remedy the crash. It's the same thing that happened when I tried to run the app made the window invisible - it didn't have the jar file added to the project. When I added it, it didn't crash.

I have several questions -

1) is the fact that I didn't include it as a source library causing the crash?

2) Why doesn't it crash when I run it from Eclipse?

3) And why isn't the MobFox window showing up in any case?

4) What changed such that the Window showed up before, and doesn't now?

The only change I can think of is that it was approved. And that it was produced by the Ant build instead of Eclipse.

Well, let's try the other ones.

3: crash

2: crash

1: crash.

Ok, let's back out the MobFox code and re-upload. It's really just the element in the layout, and the code that checks for invisible.

Good - that's done. Now, let's make sure it runs from Eclipse.

Yup. Not that it means much.

Yeah, after I upload and download the file, it's still crashing on class not found.

Ok, what's going on with the "live" code, is, it's blank because of no backfill, maybe.

Ok, what if I bypass the ant and go with the old export unsigned trick?

Well, this thing is just giving me a bunch of junk.

E/AndroidRuntime(32764): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.kanjisoft.jlpt5.free/com.jlptquiz.app.StartActivity}: java.lang.NumberFormatException: unable to parse 'For the full version, look for for "Japanese JLPT 5 Vocab Quiz" on the Android Market!' as integer

E/AndroidRuntime(32764): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1647)

It's reading the wrong variable - it's one up from the one I named. The R file got out of whack somehow.

This is the code:

String nagNumberString = appState.getString(R.string.nag_questions);

if (nagNumberString == null) {

nagNumber = 99999;

} else {

nagNumber = Integer.parseInt(nagNumberString);

}

But nag_questions is 100.

And this is only after I upload it to the Android Market. Before that it tests fine - including the signed jar installed with adb install. Hopefully, it was just a hiccup!

Same thing - I had shifted the position of it just make it regen - but didn't save it.

I saved it this time, but of course, I'm getting the same problem.

I'm thinking maybe try hardcoding it just to get a fix going, and finish tomorrow. This ain't fun.

Ok, let's pull the library, and generate it with eclipse.

Nope, that wasn't. It now look as if having two entries int string.xml, one for the shell and one for the core, with the same name, may have been the problem. Why it only turned up now, I really couldn't say.

Let's see if it compiles if I just leave it in the shell (number of questions), where it should be.

Strange - it compiles, but, the Eclipse IDE is showing a compile error.

Ok, I'll make a note to remember to delete the identical entry from the shell from now on.

Ok, I'll also remember to *save* something when I make a change to it. It's not working because of the shell.

I've completely commented out a problem section of code, but it's still managing to get executed after the upload. Not cool. Even when I clean the project, still no luck.

When I go to unpublish, just until I get the problem solved - the apps still show up on the market!

Interesting - if I start up the app again, it works..it's just crashing on the first try.

Well, let's try it with level 2. Ok, that's getting messed up on level, which may be another doubled one.

Not, but it's on the shell project. Let's put it into core for now.

I just had a thought. Since I put that whole ant build in there, it takes forever to rebuild the workspace - maybe I'm fouling things up by running the ant at the same time. Still, I was having the same problems when I was doing the release.

Ok - it now works, signed locally. But when I update the apk - same error. A messed up R file.

How can it be good on one system, and screwed up on the other? It's the same, signed apk.

Ah - I never removed jar files for MobFox on the other ones - wow - I thought I had done that.

Get rid of them and it works. Obviously, straying from the parameters of the android project instructions and adding them as a straight jar wasn't the best approach.

And that's a wrap