Hi All, Several people have found that my app doesn't load in Android and only presents a force close message from the outset. In the emulator it works. I'd be grateful for any help with testing. I don't have an Android device and can't, therefore, post any logcat, so if anyone would be prepared to try and run it for me and give me some feedback, that would really help. I can send you a zip file or whatever is easiest.

deleted

The best thing to do is to create an apk file - this is the file you would (at some date in the future) submit to Google play services for general release. There is an excellent how-to guide created by GoNorthWest in the How-to section of BT which shows you how to do this. It doesn't take long to do. Once you have created the apk, add it to dropbox or similar and I (and I am sure others) will test on our Android devices. Any questions, just shout.

Also I think logcat does still show with emulator.it should.it has nothing to do with having a device.I think its in the far right of one eclipse menu items .if its hidden thats how you would make it pop.it might also be also be by the run button.hope that helps

Sorry, I didn't read your post fully. Not sure if my suggestion is the best for your specific purpose. Anyone else advise?

GoNortHWest also has some good tutorial videos on youtube.krompa your suggestions would be helpful too

@cmc I think he is having no problems in emulator hence no logcat errors to show

Either zip up your project files, or send me an apk, and I'll give it a spin this weekend. MrkFleming at gmail dot com

Krompa true lol I feel dumb lol but yeah if its only runs good on simulator then apk is good way to test.what build settings,plugins,etc. Thats weird that it only runs on emulator

@king, best offer you will get all year from @GNW as he will probably know what the logcat is actually saying. I'm good to provide feedback and screenshots when u ready for that. @cmc - you work too hard, that's all.

Thanks everyone for the responses. Yes, as you say, I expect it needs to be run on a device but from Eclipse so to get the logcat. I'll email it to GoNorthWest (thanks) and see what he finds.

Cool well actually logcat is still shown even if there are no errors

Hi Oliver, I compiled the app using the standard debug keystore, and ran it on my Nexus 7 running Android 4.4.2. I went through every screen in the app (but not all the links), and I didn't have a single problem. That's good and bad! If your friends are having issues, it would help to know: * What devices are they using? * What level of Android are they using (from Settings > About)? * What screen are they trying to use when it crashes? That information will help us narrow things down a bit. Mark

Hi Mark, Like you say, that's good and bad. Makes it more difficult to get to the bottom of it. One of them uses a N7000 running 4.1.2. I'm just finding out about the others. Thanks very much Oliver

Oh, ok, another reply just in: Alcatel Smart Mini, Android 4.1.1, stock ROM

And the app just doesn't load in the first place. As soon as they load it, it looks like this: https://www.dropbox.com/s/cn1ybxri5ffydj1/forceclose.png

And Mark, did the map load when you went through the app? Many thanks Oliver

I have tried something suggested by another member over PM. My background image wasn't in all the drawable folders and he reckoned some phones produce the force close error if they look for it in that folder and can't find it. I can't say with confidence if that was the reason but at least one person who previously couldn't run the app now can.

Hi Oliver, It's entirely possible that a missing image might cause a force close on some versions of Android. Without the LogCat output, it's hard to say for sure. But, it's encouraging that some of your users are now having success! I don't recall a map screen in the app when I went through it...either with or without map tiles. Are people complaining they can't see it? Very nice app, by the way! Mark