Titanium Community Questions & Answer Archive

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

team development issues ubuntu and mac, GUID

I develop on a ubuntu machine and my partner uses a mac machine

I created a project and since I only have android installed configured it. my app is ready and shared the code with my partner, but he did not have the option to run the app in iphone emulator, though it is installed on his mac.

but if the app was created by him and he enabled both iphone and android sdk, it worked on my machine with android.

I have reviewed every source code and config file in the project and now I believe it has to do with GUID of the app and it is controlled by appcelerator.

what I have tried
i) I tried manually changing the GUID then the emulator options go away.
ii) I have created a new project on mac, and replaced only the resource folder from my project, the compilation starts but does not give any error and seems to hang

please suggest a way where I can salvage my completed project into a iphone deployable app

please also suggest a Team development workflow best practice

— asked November 23rd 2010 by Krishna M
  • development
  • guid
  • mac
  • team
  • ubuntu

2 Answers

  • Create the folder yourapp/build/iphone and restart Ti. The iPhone tab will then show up (on the apple machine).

    — answered November 23rd 2010 by Peter Griffin
  • This may be of some help: (http://bit.ly/9U2xKq)

    Its the work-flow we use with multi-dev which allows us to have our own setup and also solves an issue we were having with the testing.

    — answered November 23rd 2010 by Chris Nesbit
    1 Comment
    • I know this is an old question… but I am a newbie on Titanium. The bit.ly doesn't work anymore. Can you help describe the solution? I have the precise same problem as stated above.

      — commented November 19th 2012 by Shiong Gau Chan
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.