[TIMOB-2555] Android: tiapp.xml changes to android->application element only work if other manifest-related entries exist
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:59:26.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M01 |
| Components | Android |
| Labels | android, defect, release-1.6.0 |
| Reporter | Bill Dawson |
| Assignee | Bill Dawson |
| Created | 2011-04-15T03:22:36.000+0000 |
| Updated | 2011-04-17T01:59:26.000+0000 |
Description
Example: If you have this in tiapp.xml:
<android xmlns:android="http://schemas.android.com/apk/res/android">
<manifest>
<application android:debuggable="true"/>
</manifest>
</android>
... that debuggable attribute doesn't make it to AndroidManifest.xml. But if you add in something else under manifest in tiapp.xml, it does:
<android xmlns:android="http://schemas.android.com/apk/res/android">
<manifest>
<application android:debuggable="true"/>
<supports-screens
android:smallScreens="false"
android:normalScreens="true"
android:largeScreens="true"
android:anyDensity="true"
/>
</manifest>
</android>
To test:
Create app and put this in tiapp.xml (replace the
androidsection therein with this):Launch the app (don't worry about what the app does / looks like, that's all irrelevant.)
After the app has launched, open the generated file build/android/AndroidManifest.xml. Find the
<application>node in that xml file. In the failcase, you'll seeandroid:debuggable="false". When fixed, you'll see it astrue.Bill this failed for me in 2.1 Sim [INFO] Titanium SDK version: 1.5.0 (12/10/10 15:05 f08319c)
Eh? Good, you proved the fail case. Now test with master. ;) (It wasn't meant for 1.5.0)
[INFO] Titanium SDK version: 1.6.0 (01/10/11 08:25 3452f06) sim 2.2 and 1.6