{ "id": "63318", "key": "TIMOB-2686", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11237", "name": "Release 1.6.0 M04", "archived": true, "released": true, "releaseDate": "2011-01-10" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:59:48.000+0000", "created": "2011-04-15T03:27:02.000+0000", "priority": { "name": "Trivial", "id": "5" }, "labels": [ "android", "regression", "release-1.6.0", "reported-1.5.1", "services" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:59:48.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
1.5.1 + hvga skinned 2.3 emulator
\n1.Platform >android services
\n2.click strat service, then check if its running by way \"check to\nsee if service is running\"
\n3.start via \"createservice\" and check it as well
results: in both cases, the service did not start
I'm not able to reproduce the problem under 1.5.1 or 1.6.0.\nService runs fine in my tests. Can you reproduce still at will?
man, what am I doing wrong? I can accept its my issue, maybe I\nforgot how to run this test - in todays 1.5.2 and 1.6.0. Happens in\nall devices/emulators (not 2.3 specific as erroneously\nreported)
\n1.Tap \"start service via start service\"
\nresults\": see output of \"starting service via start service\"
\n2.tap \"check to see if test service is running\"
\nresults:Servie is NOT running.
same when using the other start button. Hopei am not wasting\neveryones time here.
Anything interesting in logcat?
\nAlso, how do you typically start KS? Here's exactly what I did\njust now (and it's working):
\nThen I run KS on the phone, go straight to Platform - Android\nservices and test it there.
\nI'm worried maybe you're uncovering some kind of build-time bug\nthat I'm not seeing, just because of the differences there might be\nin the way we build and start Kitchen Sink.
Hey Bill - I'm sorry its taken me so long to respond. I followed\nyour steps above and see this:
\nI/TiAPI ( 3710): (kroll$65) [1901,783069] SERVICE TEST: Starting\nvia startService
\nW/ActivityManager( 1088): Unable to start service Intent {\ncmp=com.appcelerator.pushtest/.TestserviceService (has extras) }:\nnot found
\nI/TiAPI ( 3710): (kroll$65) [6621,789690] SERVICE TEST: Service is\nNOT running
KS 1.5.1 works as expected, 1.6.0 fails. I'm going to try to\ndelete my local directory and do a clone after this pass is\nover.
ok, I have a device with a previous version of KS 1.5.1 and the\ntest works there. I republished KS on the same device using 1.5.1\nand the test now fails - meaning its media related and not sdk\nrelated.
There still could be something wrong with our build/packaging\nprocess that maybe you're uncovering by some interesting set of\ncircumstances.
When you do a build/release which then fails, can you upload the\nbuild/android/bin/app-unsigned.apk file here? I wanna see what's in\nit. Maybe the service JS file is really not getting packaged for\nsome reason.
All is well with a clone today. closing against [INFO] Titanium SDK version: 1.6.0 (01/19/11\n08:23 aa8c451) N1 (2.2.1) G1 (1.6) and sim 2.3.