Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-2686] Android: 2.3, Android services never start

GitHub Issuen/a
TypeBug
PriorityTrivial
StatusClosed
ResolutionFixed
Resolution Date2011-04-17T01:59:48.000+0000
Affected Version/sn/a
Fix Version/sRelease 1.6.0 M04
ComponentsAndroid
Labelsandroid, regression, release-1.6.0, reported-1.5.1, services
ReporterThomas Huelbert
AssigneeDon Thorp
Created2011-04-15T03:27:02.000+0000
Updated2011-04-17T01:59:48.000+0000

Description

1.5.1 + hvga skinned 2.3 emulator

1.Platform >android services
2.click strat service, then check if its running by way "check to see if service is running"
3.start via "createservice" and check it as well

results: in both cases, the service did not start

Comments

  1. Bill Dawson 2011-04-15

    I'm not able to reproduce the problem under 1.5.1 or 1.6.0. Service runs fine in my tests. Can you reproduce still at will?

  2. Thomas Huelbert 2011-04-15

    man, what am I doing wrong? I can accept its my issue, maybe I forgot how to run this test - in todays 1.5.2 and 1.6.0. Happens in all devices/emulators (not 2.3 specific as erroneously reported)

    1.Tap "start service via start service"
    results": see output of "starting service via start service"
    2.tap "check to see if test service is running"
    results:Servie is NOT running.

    same when using the other start button. Hopei am not wasting everyones time here.

  3. Bill Dawson 2011-04-15

    Anything interesting in logcat?

    Also, how do you typically start KS? Here's exactly what I did just now (and it's working):

    • Get, build and release latest 1.6.0 master.
    • Start Titanium Developer
    • Delete my existing Kitchen Sink project.
    • Import Kitchen Sink project from master's demos/KitchenSink.
    • On project edit screen, make sure 1.6.0 is selected.
    • Run on Device to put Kitchen Sink on my phone (Android 2.2).

    Then I run KS on the phone, go straight to Platform - Android services and test it there.

    I'm worried maybe you're uncovering some kind of build-time bug that I'm not seeing, just because of the differences there might be in the way we build and start Kitchen Sink.

  4. Thomas Huelbert 2011-04-15

    Hey Bill - I'm sorry its taken me so long to respond. I followed your steps above and see this:

    I/TiAPI ( 3710): (kroll$65) [1901,783069] SERVICE TEST: Starting via startService
    W/ActivityManager( 1088): Unable to start service Intent { cmp=com.appcelerator.pushtest/.TestserviceService (has extras) }: not found
    I/TiAPI ( 3710): (kroll$65) [6621,789690] SERVICE TEST: Service is NOT running

    KS 1.5.1 works as expected, 1.6.0 fails. I'm going to try to delete my local directory and do a clone after this pass is over.

  5. Thomas Huelbert 2011-04-15

    ok, I have a device with a previous version of KS 1.5.1 and the test works there. I republished KS on the same device using 1.5.1 and the test now fails - meaning its media related and not sdk related.

  6. Bill Dawson 2011-04-15

    There still could be something wrong with our build/packaging process that maybe you're uncovering by some interesting set of circumstances.

    When you do a build/release which then fails, can you upload the build/android/bin/app-unsigned.apk file here? I wanna see what's in it. Maybe the service JS file is really not getting packaged for some reason.

  7. Thomas Huelbert 2011-04-15

    All is well with a clone today. closing against [INFO] Titanium SDK version: 1.6.0 (01/19/11 08:23 aa8c451) N1 (2.2.1) G1 (1.6) and sim 2.3.

JSON Source