Here's the manifest:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2007 Google Inc.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
* See the License for the specific language governing permissions and
* limitations under the License.
-->
<!-- Declare the contents of this Android application. The namespace
attribute brings in the Android platform namespace, and the
package
supplies a unique name for the application. When writing your
own application, the package name must be changed from
"com.example.*"
to come from a domain that you own or have control over. -->
<manifest xmlns:android="http://schemas.android.com/apk/res/android";
package="com.fjmustak.android.worm"
android:versionCode="2"
android:versionName="0.1.0">
<uses-sdk android:minSdkVersion="3" />
<uses-configuration android:reqNavigation="trackball" />
<application android:icon="@drawable/icon" android:label="@string/
app_name">
<activity android:name="Snake">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category
android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
On Dec 21, 5:23 am, Mark Murphy <[email protected]> wrote:
> 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
