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 8855375
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T14:07:15+00:00 2026-06-14T14:07:15+00:00

I have released version 1.0 of my app. Version 1.1 will likely include some

  • 0

I have released version 1.0 of my app. Version 1.1 will likely include some kind of migration code. For argument’s sake, let’s say it will update a core data attribute – all last names will be converted to uppercase. I will execute this code on first launch in version 1.1.

Will I need to keep this code in place for all subsequent versions? If a user skips 1.0 and only updates when 1.2 is released, will 1.1 be applied first automatically? Or do I need to keep checking whether to update the last names in all versions forever?

  • 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-14T14:07:17+00:00Added an answer on June 14, 2026 at 2:07 pm

    You don’t release updates, you release new versions. If someone updates from 1.0 to 1.2 and skips 1.1, than that’s exactly what’s happening. 1.1 will never be installed or executed.

    EDIT:

    Here is a suggestion for a very simple way to manage updates. Probably not the most elegante one, but it works.

    NSString *lastVersion = [[NSUserDefaults standardUserDefaults]
                             stringForKey:@"LastVersion"];
    NSString *currentVersion = [[NSBundle mainBundle]
                objectForInfoDictionaryKey:@"CFBundleShortVersionString"];
    
    if ([self version:lastVersion isSmallerThanVersion:@"1.1"]) {
        // update from 1.0 to 1.1 here.
    }
    if ([self version:lastVersion isSmallerThanVersion:@"1.2"]) {
        // update from 1.1 to 1.2 here.
    }
    if ([self version:lastVersion isSmallerThanVersion:@"1.3"]) {
        // update from 1.2 to 1.3 here.
    }
    
    [[NSUserDefaults standardUserDefaults]
      setObject:currentVersion forKey:@"LastVersion"];
    

    In this example you had 4 versions (1.0, 1.1, 1.2, 1.3) and 1.3 is the newest release.

    You run this on every launch of your app. Since updating the app also terminates it, you can assume that this will run after a possible update.

    Basically you load the last version that the user used on this device from the user defaults. If the app launches for the first time ever, there will be no known previous versions, none of the update routines are executed and the current version (1.3) is saved as the last used version.

    If the app was used with the previous version (1.2), then lastVersion will be 1.2 and only the last if block is executed.

    If the app was used with version 1.1, but skipped 1.2 and was now updated to 1.3, lastVersion will be 1.1 and the last two if blocks are executed sequentially. So first you update your data from 1.1 to 1.2, then from 1.2 to 1.3.

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

Sidebar

Related Questions

i have released a version 1 on some app in the market. Can anyone
Say I have app version 1.0 released on the app store. Then I want
I have a Windows Form application. Version 1 of my app has been released
Here's the situation: I have just released a minor version (3.5.3) of my app
I am a question about plist. If i have already released an app say
I have released two versions of my app successfully. But after third version of
I have released my app update with push notifications however when I check my
Recently I have released my app into the US AppStore. Now I Planed for
There are some processors out there that don't have commercially released documents explaining what
I have this releases table in a SQLite3 database, listing each released version of

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.