[TIMOB-2476] Android: tiapp.xml Javascript Activity Elements Must Allow for Normal Android Elements
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:59:13.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 M04 |
| Components | Android |
| Labels | android, feature |
| Reporter | Don Thorp |
| Assignee | Bill Dawson |
| Created | 2011-04-15T03:20:47.000+0000 |
| Updated | 2011-04-17T01:59:13.000+0000 |
Description
url needs to be considered an "additional"
attribute to be replaced and the standard
android:configChange entry for Titanium added.
Everything else should be put in the generated activity element as
entered by the dev and supported by Android.
Marking as a feature as this was not fully specified in the original ticket.
(from [eeefa79aede8df2967c92590ea7c1f673ab8347e]) [#2476 state:fixed-in-qa] Include sub-nodes of js activity elements from tiapp.xml and move them into AndroidManifest.xml as-is. https://github.com/appcelerator/titanium_mobile/commit/eeefa79aede8df2967c92590ea7c1f673ab8347e"> https://github.com/appcelerator/titanium_mobile/commit/eeefa79aede8...
To test, create a new project, then edit the tiapp.xml and replace its 'android' section with this:
https://gist.github.com/6b628215e36644edab6f">https://gist.github.com/6b628215e36644edab6f
Then launch the app. It doesn't matter what the app actually does, we want to look at the build/android/AndroidManifest.xml that is generated during the launch process. If you open that file in the failcase and search for 'Myactivity', you won't see the 'intent-filter' xml element below the Myactivity 'activity' element. In the fixed version, you will see it, like this:
https://gist.github.com/7f8ac6b22738e812a4ec">https://gist.github.com/7f8ac6b22738e812a4ec
awesome, closing - [INFO] Titanium SDK version: 1.5.0 (12/08/10 10:08 7d08f15)