Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9213895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T01:51:18+00:00 2026-06-18T01:51:18+00:00

My iPad app currently uses Settings.bundle to allow settings both via the built-in Settings.app

  • 0

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?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T01:51:19+00:00Added an answer on June 18, 2026 at 1:51 am

    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.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I currently have one iPad app, but it now needs to become two. The
I have recently built an iPad app using PhoneGap. Currently it saves the last
Am currently developing an iPad app which uses a UIScrollView. The UIScrollView is populated
I want to add a splashscreen within an App that is an iPad-App currently.
I have an iPad app that was built in Adobe Air, the app currently
My iPad app is currently built as such: xml data is pulled from my
I'm currently creating a iOS 5 iPad app where there will be heavy network
I'm developing an iPad App & currently testing it on the device itself -
I currently prepare an existing iOS app for the new iPad with iOS 5.1
I'm currently working on an OpenGL ES 1.1 app for the iPad its running

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.