7

My iPad app currently uses Settings.bundle to allow settings both via the built-in Settings.app as well as via InAppSettingsKit. I now want to switch to IASK entirely and disable the built-in settings. I have renamed the Settings.bundle folder to InAppSettings.bundle, but when I deploy this new version to my test device, the old Settings data seems to stick around - at least, I can still access the old settings via Settings.app.

Is there a way to force removal of Settings.bundle when a new version of the app is installed?

Gereon
  • 17,258
  • 4
  • 42
  • 73

1 Answers1

9

Make sure you do a clean build in Xcode. For development builds, you also need to remove the app from the Simulator or device first. Otherwise old files are left in place.

rmaddy
  • 314,917
  • 42
  • 532
  • 579
  • 1
    This also happens with clean builds. Removing the app isn't really a viable option for users who update via the app store. – Gereon Jan 27 '13 at 07:59
  • 1
    Deleting the app is only needed in development. Real users doing an update won't need to delete the app. – rmaddy Jan 27 '13 at 08:01