Hi guys, I have got my first Android app on google play but it wont load on my newly obtained HTC Wildfire. This ancient android device is running 2.2.1 I'm wondering if this just an issue with the device or if i've done something wrong with the apk. I'd be grateful for people to download and test for me if possible please, and report back. It is a free app. Many thanks. https://play.google.com/store/apps/details?id=com.scootfest&hl=en_GB

Sorry dude. On my Galaxy Tab 2 7" Tablet running Android 4.1.1 it launches for a second, stalls as if it's waiting on a process, and dies with "Unfortunately, Scootfest has stopped". Cheers! -- Smug

Same here mate, sorry. Tested on wildfire 2.2.1 and One X 4.1.1 Also a lot of permissions that I guess you're not using? If I didn't 'know' you I wouldn't install it! Things like: Read contact data, write contact data modify/delete sd card contents hardware controls discover known accounts. You can remove permissions that you don't use in the manifest.xml, the less permissions the better.

Thanks Smug! Any idea what I've done wrong? Must be something with the release .apk?

@raveyd, cheers. What have I done wrong with the release package? iOS will not post an app that wouldnt work on the device! I've clearly done something wrong here! Thanks in advance!

Hard to say really, could be any number of reasons. You should be able to get a pretty good logcat report though, with your wildfire plugged in as an emulator.

Cool, cheers!

Logs are my only friend in Android. Otherwise, I'm only guessing. With my android apps, similar behavior has appeared in connection with Network Access and GPS Access, but that's just a stab in the dark. Cheers! -- Smug

I get the same message.

Could be a parse build path issue.

No luck here either. But I have an idea, as I know we were discussing push a couple of days ago. I found out parse push was causing instability in my latest app with the 1.3.1 sdk - the app would compile, but would bomb out on startup. I worked out today that if I tick everything in the configuration options when adding the sdk jar to the build path, my app doesn't crash. Worth a try? btw, I run an ancient Android device with 2.2 as well. I figure if my app works on that, it is a good test.

@Alex, maybe you should unpublish the app for now? The error's starting to look consistant. No point potentially getting bad feedback before you've even started. Would be Sods law that your first ever android feedback is abusive filth! You should run logcat to find out what's happening, anything else is really just guesswork. It could be parse, it could be something else..

I have the same issues it crashes a launch. Are you using a splash screen? I know that has at times caused me much grief :/

Cool thanks for the advice, just unpublished it. I'm all plugged in now, going to do some testing. Proof that you simply cannot rely on the emulator. @mysps - Yup, running ,splash screens too :/

I've heard a lot of people suggest splash screens cause a problem on Android. It may have done in the past, but I've never had a problem with splash myself. Easy thing to pull out though as a test.

Well, it runs absolutely fine on the device! https://dl.dropboxusercontent.com/u/63458265/Screen%20Shot%202013-07-18%20at%2022.34.41.png

What did you change?

Nothing! So thats no clearer!

What we also have is 'Sorry, the video cannot be played' on youtube plugin. The error is 07-18 23:16:30.952: E/AVCDecoder(72): Video resolution too high, reject it Do I take it that to play the high res vids the device needs to be a certain spec? If I know what that is I can include it in the metadata. Cheers!

Fixed on the store with @alanmac's suggestion, thanks.

Hi Alex - Splash or Parse?

Parse :) Splash has remained in tact and works fine :) Thanks again.

No worries, I know what its like trying to get these things to gel! I'm currently struggling to upgrade an old app that has admob and it appears that parse doesn't want to play nicely with it.

Oh dear. Look forward to that when the time comes! Actually, I think i'll just bin parse if its too much of a pain. Push is useful but I dont find it critical. The issue i'm having now its simply loading Twitter. All URL options seem to load a blank screen!

Parse is the best push solution I have come across, it's probably me. The problem is that just when you think you have something sorted, it changes! Twitter - I had grief with that too lol!

Think I'm going to bin it, just wont work! I have to say, iOS is so much better a platform to develop on - In my short Android experience!

Android is a bit frustrating, but so is IOS sometimes! What are you trying to do with twitter? I have in the past been able to display peoples tweets, but nothing very fancy.

Just fixed my IAD + Parse problem. I spent ages fiddling around, I think in the end it was the order in which I added the SDK's - well, it *seemed* to be the problem. One day I'll try to understand, today I am just happy its done!

Good work Alan. Just trying to display a twitter users page, nothing remotely fancy!!

So I thought I'd give scootfest another go. It runs now, but I hate to tell you, but I think you have the 'spinner of death'. Check out this thread - the commenting out technique is the best fix imho http://www.buzztouch.com/forum/thread.php?tid=A36B676431E081455275128

Any specific page? It works fine on mine, downloaded from play as opposed to the dev version. Cheers

I updated from Play too. Yesterdays version wouldn't start, today I got further. Not sure where I was. I remember there was a changing background, a menu down the middle and thats about it, I then couldn't operate the app any further.

Great! I'll see what comes in from users! What would be the issue now? Impossible to know as it works fine on mine and therefore I get no error reports at all :/