Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

AddRunningClient starting device on non-zero client count

Hi, using Ti mobile SDK v1.3.3, iOS 4.0 receive the above error when building. What does it mean? Do I need to do anything to address this error before submitting this to Apple?

Thanks for all input/help!

— asked July 2nd 2010 by karlo kilayko
  • 1.3.3
  • 4.0
  • iphone
  • mobile

1 Answer

  • I don't have an answer but I get the same message when running my app (SDK 1.3.3, iOS4). In my case, it occurs the first time I play a local sound file. The message shows in the log (when running in the simulator) and then there is a few second delay before the sound plays. Any subsequent playing of a local sound file works fine (plays immediately) and doesn't throw the message. I'm going to try playing a null sound file when the app loads to see if that eliminates the delay the first time I play a "real" sound.

    Oh, I loaded my app to a device and the delay is also there, so it's not related to the simulator. And the message doesn't seem to be an "error", just some sort of debugging message?

    var sound = Ti.Media.createSound({url:"bottle_pop_1.mp3"});


    — answered July 7th 2010 by Joe Bossalini
    • I added the playing of a "blank" mp3 file at the beginning of my app.js and, though I still get the message in the log, the first play of a "real" audio file works fine now without delay or message. Got the blank mp3 from here: http://www.xamuel.com/blank-mp3s/

      — commented July 7th 2010 by Joe Bossalini
    • That's interesting. The app on which I'm getting the error does use sound. I like the "blank sound" workaround suggestion! I have submitted the update to Apple already, so if it gets rejected, I'll try that solution.

      — commented July 7th 2010 by karlo kilayko
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.