Titanium Community Questions & Answer Archive

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

Problems with AndroidManifest.xml not being updated

My androidmanifest.xml does not appear to be getting updated.

I change the version number and save it, run the app in the emulator.

Check the file, same as it was before I changed anything.

If I delete the file, it IS recreated but with the versionCode and versionName reset back to 1 and not the current version/build:


The version could should increment and the version name should be what I have in the Titanium settings.

At present to publish I am having to change these manually but I am wondering what else is not being changed?

Is this a bug in 1.3? or is it something I am doing wrong?

— asked June 13th 2010 by Stephen Page
  • android
  • androidmanifest
  • androidmanifest.xml
  • fails
  • manifest
  • not
  • publish
  • to
  • update
  • updating
  • versioncode
  • versionname

2 Answers

  • Editing your tiapp.xml file is a lot easier than maintaining custom manifests. During build it outputs a manifest with the parameters in it.

    <?xml version="1.0" encoding="UTF-8"?>
    <ti:app xmlns:ti="http://ti.appcelerator.org">
        <android xmlns:android="http://schemas.android.com/apk/res/android">    
            <manifest android:versionCode="2"
    — answered September 22nd 2012 by Jean-Rene Auger
    1 Comment
    • Thanks! Modify tiapp.xml is the solution

      — commented October 29th 2013 by henry manco
  • Check in the Programing Guides section. You need to rename the AndroidManifest.xml to AndroidManifest.custom.xml and make your changes there.

    — answered June 13th 2010 by Don Thorp
    1 Comment
    • I am also having the same issue. I tried this but it creates a .gen file and still forces

      when I use titanium to distribute. I am new to recompiling outside of titanium so I am not sure what to do next. I need to put up bug fix update to an app on the Market. I cannot because of this versioning issue.

      Any easy way out?

      — commented December 27th 2010 by salim ibrahim
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.