Titanium Community Questions & Answer Archive

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

Change info.plist after packaging

Hi there,

So I've just sent my first app to Apple for approval.

The app name is a little long, so for the next update I'd like to change the app label on the homescreen to something shorter.

So how can I change the Info.plist file after packaging my app in Titanium Developer? I've already tried to unzip, "Show package contents" on the .app file, edit Info.plist and zip the .app file again, but if I upload this new zip to Apple, I get an error message saying it's not signed or something.

Thanks in advance.

— asked April 2nd 2010 by Doney den Ouden
  • app
  • distribute
  • distribution
  • info.plist
  • iphone
  • label
  • mobile
  • name
  • package
0 Comments

4 Answers

  • Does really nobody know the answer?

    — answered April 4th 2010 by Doney den Ouden
    permalink
    0 Comments
  • Did you ever figure this out? I'd love to know the answer too.

    — answered June 29th 2010 by Christopher Rumpf
    permalink
    1 Comment
    • Well, I didn't figure out how to change the .plist file. BUT, what you CAN do is the following: Create a new project with your new project name, then copy the Resources folder from your old project to your new one :)

      — commented June 30th 2010 by Doney den Ouden
  • hello… wow, 4 months and no answer. i would like to also know if this is possible. i would like to release a "lite" version of my app, but i don't want the actual name on the device to be different (just the icon). is this possible? i imagine it might be the same thing.

    — answered August 1st 2010 by paul seymour
    permalink
    0 Comments
  • I would imagine that the signing of the app, is so that you can change nothing after. I think that Apple will not accept it if it has been tampered with.

    — answered June 28th 2011 by Sky Apperley
    permalink
    0 Comments
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.