ios - Unreleased xcdatamodel versions and lightweight migration -


if have multiple unreleased xcdatamodel versions between release , release b, lightweight migration still work once release public if delete unreleased versions?

here's more discrete example:

xcdatamodel version 1.0  --> release public xcdatamodel version 1.1  --> unreleased (based on v1.0) xcdatamodel version 1.2  --> unreleased (based on v1.1) xcdatamodel version 1.3  --> release public b (based on v1.2) 

i want make sure when submit release b, users coming release migrated properly. or terrible way go it? understand if didn't care data on testing devices, base xcdatamodel version 1.3 on version 1.0 , put new in version - don't want lose data on testing devices have had versions of app v1.1 , v1.2 on device.

thanks!

assuming format used existing user data can converted current format via automatic lightweight migration, doesn't matter created internal, unreleased versions.

what need include in released app: every version user might using. in case looks people have 1.0-formatted stores, there's no need include 1.1 or 1.2. if that's not case-- i.e. if there's user out there somewhere might have version 1.1 or 1.2 data-- need include them.

so, long 1.0 --> 1.3 changes work automatic lightweight migration and no users have 1.1 or 1.2 format data, delete intermediate versions.


Comments

Popular posts from this blog

plot - Remove Objects from Legend When You Have Also Used Fit, Matlab -

java - Why does my date parsing return a weird date? -

Need help in packaging app using TideSDK on Windows -