1

I'm responsible for re-signing apps, which our vendors create, with our Enterprise cert and then distributing them internally. The last time we had an update to an existing app, users had to uninstall the old version before installing the new one otherwise they would have two identical looking apps on their home screen.

What do I need to change and/or keep the same in the manifest.plist file so future app updates overwrite the existing app? Do I need to do anything different with the Provisioning Profile?

In light of the manifest cache bug in iOS8, will changing the bundle-identifier make what I want impossible?

Community
  • 1
  • 1
MJA
  • 350
  • 1
  • 3
  • 15

2 Answers2

2

You need to keep the app's bundle id the same. That's all that matters for the app to be treated as an update. If the bundle id changes then it gets installed as a new, separate app.

rmaddy
  • 314,917
  • 42
  • 532
  • 579
  • I'm not sure 100%, but you might want to add that not only the "bundle identifier" as it appears in Xcode (e.g, `com.myCompanyName.MyAppName`) needs to be the same, but also the prefix (e.g., `D2D4T4F87R`, seen in the Developer portal). – Nicolas Miari Jan 07 '16 at 04:59
  • Sounds like the work-around to the iOS 8 caching issue then screws up effective app updates. Does the bundle-version make any difference? – MJA Jan 07 '16 at 05:06
  • 1
    @NicolasMiari the team identifier is not needed in the manifest.plist file. Pretty sure that comes in from the Provisioning Profile (App ID + Cert) – MJA Jan 07 '16 at 05:08
  • Yes; I meant that he should use the same provisioning profile (or another one created with the same prefix + bundle id). – Nicolas Miari Jan 07 '16 at 05:10
  • I missed the "manifest" part of the question. My clarification was intended as generic app distribution. – Nicolas Miari Jan 07 '16 at 05:15
0

Only bundle ID (e.g. com.abc.xyz) needs to be remain same.

Nilesh Patel
  • 6,318
  • 1
  • 26
  • 40