[TIMOB-2568] Android: Service "type" attribute in tiapp.xml accidentally making it into AndroidManifest.xml
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:59:28.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:23:02.000+0000 |
| Updated | 2011-04-17T01:59:28.000+0000 |
Description
You define an Android Service in tiapp.xml with a block such as this:
<android xmlns:android="http://schemas.android.com/apk/res/android">
<services>
<service url="myservice.js" type="interval"/>
</services>
</android>
When build the app, the type attribute above is
accidentally making it into the generated AndroidManifest.xml as
service_type. It's confusing and ugly but doesn't
actually hurt anything. It looks like this:
<service
android:name="com.billdawson.myservice.MyserviceService"
service_type="interval"
/>
So that service_type attribute should
not be there.
To test this, just make sure that
service_typeis not in build/android/AndroidManifest.xml when you launch the app (after installing the fixed SDK).using [INFO] Titanium SDK version: 1.6.0 (01/04/11 08:01 e49700d) I see only:
<service
android:name="com.appcelerator.simpleStub.MyserviceService"
/>