So I've been having a lot of trouble with my apps since the switch to 3.0. I finally realized that my app seems to be crashing when it is trying to communicate with BT Servers. I found this out because the only option that works is the 'call us' feature. Anyone else have a similar problem? If so, what is the solution? Thanks in advance!

What are your logs telling you? Do you have any log entries 'right before' it crashes? That usually gives you a hint about what happened to make it crash. Cheers! -- Smug

Here is the logcat from yesterday: 02-19 15:21:42.077: E/AndroidRuntime(2070): FATAL EXCEPTION: main 02-19 15:21:42.077: E/AndroidRuntime(2070): Process: com.c3800mt, PID: 2070 02-19 15:21:42.077: E/AndroidRuntime(2070): java.lang.StackOverflowError 02-19 15:21:42.077: E/AndroidRuntime(2070): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method) 02-19 15:21:42.077: E/AndroidRuntime(2070): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:547) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.content.res.Resources.getCachedStyledAttributes(Native Method) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.content.res.Resources.access$000(Resources.java:73) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.content.res.Resources$Theme.obtainStyledAttributes(Resources.java:1365) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.content.Context.obtainStyledAttributes(Context.java:413) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorInflater.createAnimatorFromXml(AnimatorInflater.java:122) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorInflater.createAnimatorFromXml(AnimatorInflater.java:93) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:72) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.loadAnimator(FragmentManager.java:743) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:958) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.AnimatorSet.start(AnimatorSet.java:605) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:980) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.app.FragmentManagerImpl$5.onAnimationEnd(FragmentManager.java:974) 02-19 15:21:42.077: E/AndroidRuntime(2070): at android.animation.Animato

I am not skilled in the Android troubleshooting realm. In looking at the log output, I don't see anything insightful. Let's hope someone smarter comes along to help. If you want to try an experiment, make a brand new project with just one simple screen in it.

Not much to tell... I can compile the app, and launch it. But if I go into any of the options besides 'call us' the app crashes. This is what lead me to believe that it's having problems communicating with the BT servers since that one option doesn't have to communicate with the BT servers...

Have you tried my suggestion above?

It's gotta be something else… When an app 'phones home', the 'main' task is to see if there is an update available for the app…. If it finds one, it asks you if you want to update (if it needs an update). If it 'calls' and doesn't reach… it just falls back to the last known 'good' config.txt file it has… It may be that you need to 'manually' update your config.txt file in your project… if you have radically changed your app, and the configuration doesn't show that, odd things can happen. In your Control Panel, obtain a 'new' configuration file by going to 'configuration' or 'json', and copy the entire config (a lot of funky json). I usually parse it through Jsonlint.com to make it look pretty, and then replace my current BT_config.txt file with the contents. I can't find a reason why your app is crashing with those log entries, but the third line is a 'java stack overflow' error, which usually means it tried to count something that didn't add up… again, make sure you have the most recent config file in your app. If you've added screens since the initial download, you may just need to download a 'new' copy of the project and start again. Let us know how it turns out… Cheers! -- Smug

Hi Mike, (Sent you an email on this) I tested the app out on my Nexux 7 tablet, and it crashes for me as well. I looked through the LogCat output, and I'm almost certain that the crashing is attributed to the various transitions you have specified for different pages. Here is an example from LogCat: 02-21 22:14:09.314: W/ZZ(5215): BT_viewUtilities:getEnterTransitionFromType Transition Type: "curl" And here's an example from your BT_Config.txt file: {"itemId":"DEC1FEA36BB0B1D77730996", "itemType":"BT_menuItem", "loadScreenWithItemId":"C700B23ADCDE4891D7DD2F9", "titleText":"Ruach", "imageNameSmallDevice":"news.png", "transitionType":"curl", "imageNameLargeDevice":"news.png"} If you remove those transitions (they work in iOS, but not in Android), I bet the app will stop crashing. Mark

oh. how odd. and of course I realize this 'after' Mark pointed it out. While working on my 'location menu' plugin, It would crash when I called a menu item. Drove me nuts. Found out, *any* transition (fade, curl, what have you) was killing it. Remove the transition, and it's all good. Wasn't sure if it was me, BT or what… but I figured I'd deal with it later… later hasn't arrived yet. Cheers! -- Smug

Yep! Android just doesn't deal with the transitions well at all. Not sure if there are any cross compatible transitions that could be used between iOS and Android, as I haven't researched it yet. Another thing to put on my list! Mark

Good catch Mark! Nice flashback, Smug! Let's hope that cures his ills. :-) I keep wondering if Android is worth the effort. This feels like yet another nail in the coffin. No worries, I will muster up the gumption for Android in March! Keep on trucking -- Niraj