FJMustak wrote: > In my manifest, I defined <uses-configuration > android:reqNavigation="trackball">, and when I published my game, I > got a user comment saying the game force closed on him. I used that > configuration specifically because I only had access to phones with a > trackball (G1 and Google Ion). How is it possible that a DROID user > was able to see it in the market with that attribute set (a droid has > a D-pad, and not a trackball)? Could that have caused the crash? > I subsequently restricted Droids by using "supports-screens", until I > can test it out correctly. > Any ideas why the Droid user was able to see it? Or if the > reqNavigation attribute could have caused the crash on a phone with no > trackball?
Could you post your entire manifest, or at least the portion from the top until where your <uses-configuration> element resides? You might also consider adding in some top-level exception handlers tied to an exception logging service -- I mention a few here: http://www.androidguys.com/2009/11/16/diagnosing-sporadic-errors/ That way, you'd have your stack trace to examine. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Consulting/App Development: http://commonsware.com/consulting -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
