Posted this before any luck? java.lang.NullPointerException BT_viewUtilities.updateBackgroundColorsForScreen() Error: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.idragracenews/com.idragracenews.BT_screen_menuList}: java.lang.NullPointerException at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1696) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1716) at android.app.ActivityThread.access$1500(ActivityThread.java:124) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:968) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:130) at android.app.ActivityThread.main(ActivityThread.java:3806) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:507) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.NullPointerException at com.idragracenews.BT_viewUtilities.updateBackgroundColorsForScreen(BT_viewUtilities.java:37) at com.idragracenews.BT_screen_menuList.onCreate(BT_screen_menuList.java:137) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1660) ... 11 more

Checked my other app and it has 138 reports, more bugs than beetle juice

This is were the error is generated? Please help someone //updates a screens background colors and image... public static void updateBackgroundColorsForScreen(final Activity theActivity, final BT_item theScreenData){ BT_debugger.showIt(objectName + ":updateBackgroundColorsForScreen with nickname: \"" + theScreenData.getItemNickname() + "\"");

Hey @BigFish, This particular crash, related to BT_viewUtilities.updateBackgroundColorsForScreen() , is known by the buzztouch crew, and they are working on a fix (no ETA though). In the meantime, a workaround would be, on screens that have a background color configured, to remove that color specification and just leave it blank (the default). That should prevent the Activity from crashing (but of course you're pretty screen color will be gone as well). Mark

This is were the error is generated? Please help someone //updates a screens background colors and image... public static void updateBackgroundColorsForScreen(final Activity theActivity, final BT_item theScreenData){ BT_debugger.showIt(objectName + ":updateBackgroundColorsForScreen with nickname: \"" + theScreenData.getItemNickname() + "\"");

Yep, it's in that area. The Activity crashes when trying to modify the view before it's onscreen. No fix yet, and the only workaround is to remove background screen colors in your Android app. Mark

So if I have a color background on each screen remove that or just under theme? Thanks for the reply

To be safe, I'd remove it everywhere. The theme is supposed to override individual screens. So, if you remove from theme, then the what's specified on the screen goes into effect. If you have it specified in both locations, I'd remove them both. Test also to make sure things still look good in your app after you revert to the default black background. And know this is just a workaround that...well...may not work in all cases if there is something else amiss that we haven't learned yet. Mark

@GoNorthWest is right, but here is something else you can try...I have had the same errors. I not only removed the backgrounds but also all images except the splash. The splash I made into a lesser quality jpg (figuring it would load faster) and though i am still getting the crash, it is not NEARLY as often.

It *should* only happen with background colors...but it for sure sounds like something else is contributing as well. For what it's worth, I do know that the buzztouch team is working on it. Mark

Lets see no images, no background, no splash screens, no rss feeds, no twitter, What are your apps blank? This background issue has been around for months........... glad to hear your apps are not crashing as much, lol

That's why I focus on iOS! So much more robust!

Ya but, build them in iOS and they want it in Android build them in Android they want them in iOS. I have been using Red Foundry for iOS I like it a lot. Thanks

@Bigfishtools Maybe Red Foundry for Android too? Not trying to be a jerk, but the post about the "not this, not that, blank apps" kinda got me so I figured I'd jab ya' a bit ;-) For sure we've got lots going on and for sure the list of "issues" grows and grows. The fact is, if you're going to make iOS or Android apps you're going to have to figure out the best approach. Using FREE and open source code has it's benefits, and it's drawbacks. Android is a major pain and each "feature" we create severs thousands of folks successfully - hundreds unsuccessfully. In almost all cases (with Android) you'll need to do some debugging, testing, tweaking, changing to determine what will / won't work for your particular situation / need. We wish we could magically make your app not crash - we can't. K, vented, feel better now and still dig the fish pic! LOL

David, Removed the background colors and this has taken care of the errors. Thanks Alton

Have you tested with different variations to isolate the problem. Using background in theme Not using in theme. It or only a problem when theme and screen settings are used? Fred

Yes, I have removed anything that has to do with backgrounds...........

Can you use theme only?

Sorry don't understand theme only? thanks

If you only use bg in theme does it crash? Are crashes specific to any device or OS ?

the only thing pertaining to background in theme is color #000000 No clue what kind of devices......... I have no problem with my DroidX As for OS all android I use redfoundry for iOS no problems what so ever. here are some of the comments I'm getting, makes both of us look real good huh? May 13, 2012 7:21:24 PM 1.0 db.. May 13, 2012 5:10:58 PM 1.0 just downloaded today....already a forced stop????? middle finger salute! May 12, 2012 9:35:41 AM 1.0 really guys come in! Apr 22, 2012 9:12:11 PM 1.0 do smething about this i payed goodoney 4 this game thanks Apr 22, 2012 9:09:29 PM 1.0 dos not wont to work

"Make both of us look real good huh" - who are you referring to here? Sounds like the background color crash is still happening on some devices when running your app. Or, could it be something else? Your post about removing the background colors and it "fixing it" didn't quite do it. Not sure where to begin...

And how much stock can you put in comments from people who say things like "wont to work" and "do smething"? Crazy!

David what do you want? Ya, I'm referring to the both of us. Your the guy that says all the issues is everything/everybody/android's fault. But has his copyright on the top of the scripts. I have posted the errors. I have posted them a few times on different threads. Is what is posted above not good enough? Did you read from the start or just that last post? What else would you like to see? Hey look at my app fix it tell me what's wrong. If I have done something wrong then blast me with humiliation all over your forum, at least the "know issue" will be fixed. Here is a post from GoNorthWest from above and now he's calling me Crazy???? What the hell? Then again how much stock can you put in comments from people who say "is known by the buzztouch crew" as he has stated again in a post below. Is it only known by him? He's right I'm Crazy. Again my question is what else do you need from me being that this "is known by the buzztouch crew" Hey @BigFish, This particular crash, related to BT_viewUtilities.updateBackgroundColorsForScreen() , is known by the buzztouch crew, and they are working on a fix (no ETA though). In the meantime, a workaround would be, on screens that have a background color configured, to remove that color specification and just leave it blank (the default). That should prevent the Activity from crashing (but of course you're pretty screen color will be gone as well). Here's some post for the same issue, I can find more if you like, but why put an effort into it if your not. http://www.buzztouch.com/forum/thread.php?tid=F99238BD710A25F7A8D375B&command=isSearching&currentPage=1&topicTitle=updateBackgroundColorsForScreen&createdBy=&repliedBy=&minViews=-1&maxViews=-1&minReplies=-1&maxReplies=-1&forumCategory= http://www.buzztouch.com/forum/thread.php?tid=F57C82B957F679D869FFB6D&fid=79A3D47D59E2A7B06AB0970&sortColumn=FT.id&sortUpDown=&currentPage=1 http://www.buzztouch.com/forum/thread.php?tid=1F58A78254F2A96FEBF150C&fid=79A3D47D59E2A7B06AB0970&sortColumn=FT.id&sortUpDown=&currentPage=1 At least I said both of us. Fix the "know issue" you will never hear from me again. Promise Good Luck

Hey @Bigfishtools, To be 100% clear, I was in no way calling you crazy. That comment was directed at the people who left reviews on your app, and the way in which they do so. I apologize if it seemed otherwise. I think I was also the one who mentioned "is known by the buzztouch crew." It is a known issue, but has not been solved yet. It would be nice to have a solution for sure, and I believe @David has given it a look, but the solution appears to be a bit elusive. Not sure what else to say about that. I really do apologize for giving you the impression that I was calling you crazy. That literally was not my intent. Hope you stick around buzztouch. There are some great things going on here. Mark

You must remember BTv1.5 was officially listed as beta. BTv2.0 has just been released. Other sites have their issues. It a really complex world. Buzztouch is open source. It's as much our obligation to fix and enhance Buzztouch as it is David's. A bit more effort in isolating the problem will help others help you. Even iOS 5.01 has major problems, it's the nature of the app world. Fred

@GoNorthWest, thanks for clearing that up. @Fred I almost put in my last post "what do you expect for free" and should have, another typical answer mentioned twice in this thread. As for helping I do all the time there are a few apps from members out there where I helped or added admob to their apps. I help where I can for sure. Like i posted above what else do you need to fix this issue, I have posted it on other forums like........... forget it I give. Thanks anyways.

I appreciate and see you helping others. I would suggest more attempts to isolate the problem. If the problem is sufficiently identified, that's when I see what was obvious all along. Fred

I think the problem has been pretty much isolated...it's related to setting the background color for an app: BT_viewUtilities.updateBackgroundColorsForScreen The best we non-programmers can do at this point is to figure out what combinations of screen colors do and do not cause the null pointed exception. That allows for a workaround, but nothing else, and doesn't guarantee we didn't miss something. What needs to happen now is for somebody skilled in Java and Android to figure out a fix. I do know David has looked at it, and I do know the fix is a bit elusive. If anybody out there has programming experience, I'm sure David would appreciate the help! Mark

Mark, I agree. I was hoping other post on other forums would give us an answer but no luck. I am not giving up I'm just going to find help else where. I still say it has something to do with this //updates a screens background colors and image... public static void updateBackgroundColorsForScreen(final Activity theActivity, final BT_item theScreenData){ BT_debugger.showIt(objectName + ":updateBackgroundColorsForScreen with nickname: \"" + theScreenData.getItemNickname() + "\""); Thanks

I suspect your are correct about the problem. Just need to find somebody fluent in Java who can help! Though I don't think it's a trivial fix, or @David would have fixed it already. Good luck, and keep us posted! Mark

Mark, I reposted on stackoverflow again today and got the following. What to do with it and what is means I have no clue, but might help someone that does to trouble shoot: I have no idea what your code is doing but the fix is simple: //updates a screens background colors and image... public static void updateBackgroundColorsForScreen(final Activity theActivity, final BT_item theScreenData){ if(BT_debugger != null && theScreenData != null){ BT_debugger.showIt(objectName + ":updateBackgroundColorsForScreen with nickname: \"" + theScreenData.getItemNickname() + "\""); } else { Log.e("YourApp", "Warning null var, command not completed"); } } To debug the error you could do: //updates a screens background colors and image... public static void updateBackgroundColorsForScreen(final Activity theActivity, final BT_item theScreenData){ if(BT_debugger != null){ if(theScreenData != null){ BT_debugger.showIt(objectName + ":updateBackgroundColorsForScreen with nickname: \"" + theScreenData.getItemNickname() + "\""); } else { Log.e("YourApp", "theScreenData was null, command not completed"); } } else { Log.e("YourApp", "BT_debugger was null, command not completed"); } }

Hey, Doesn't look like a fix to me (no new real code), but rather enhanced debug information. Let me try and mess around with it this weekend, and see what happens. Got a long weekend, so hopefully I can get to it. Mark

Ya your right only for debugging but heck someone knows how to make it debug just might help. Thanks for looking. Alton

I solved this problem using a image in the background, a little box of 50x50 px (with the color i need). Maybe it could help.