Databases
StackOverflow2013
Postsdbo
POSome devices ignore string resource in Manifest, Parse Error
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSome devices ignore string resource in Manifest, Parse Error
    text
    copied!<p>Trying to set orientation in manifest file, using a string qualifier</p> <pre><code>android:screenOrientation="@string/orientation" </code></pre> <p>Works on an 4.0 asus tablet, but fails on both a 2.1 wildfire and 4.1 Galaxy S. The problem is infact linking to a resource, If portrait is typed in it works.</p> <p>Ive tried changing the qualifiers used in the tablet to test on the phone. This means the exact same code, resources and layouts are used for all devices. So it cant be spelling mistakes or build issues. But it still fails on the phones and not the tablet. This seems to be yet another bug in android.</p> <p>Gives the error below, nothing in logcat</p> <pre><code>Installation error: INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION Please check logcat output for more details. Launch canceled! </code></pre> <p>Manifest section</p> <pre><code>&lt;activity android:name=".MainActivity" android:screenOrientation="@string/orientation" android:label="@string/app_name"&gt; &lt;intent-filter&gt; &lt;action android:name="android.intent.action.MAIN" /&gt; &lt;category android:name="android.intent.category.LAUNCHER" /&gt; &lt;/intent-filter&gt; &lt;/activity&gt; </code></pre> <p>I know I can do it programatically. But theres another issue with the wildfire, not restarting immediately. Instead it waits for views to be setup etc. This doesnt occur in the other devices.</p> <p>Googled and found a few others using the methods, but they dont seem to have discovered any problems. <a href="http://capdroid.wordpress.com/2012/07/21/different-screen-orientation-on-different-screen-size" rel="nofollow">http://capdroid.wordpress.com/2012/07/21/different-screen-orientation-on-different-screen-size</a> </p> <p>Thanks</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload