Details:
I renamed my target which was set up core data stack with method setupCoreDataStackWithAutoMigratingSqliteStoreNamed: and after that i was informed that all users were "lost" their data. After quick investigation i found out that MR creates data base at path Application Support/{name_of_target}/. So I had to make merge and be sure that all users will be able to "return" their data back.
Well, this is REALLY bad solution for that feature. Why did you choose that way? There are much better solutions like using bundle identifier. Of course it can be changed too, but this case is much rare then renaming of target. Or you can save it in the root of 'Application Support' folder. Or at least you can provide docs to your methods in Xcode with warning and explanation of how your methods is working.
Details: I renamed my target which was set up core data stack with method
setupCoreDataStackWithAutoMigratingSqliteStoreNamed:
and after that i was informed that all users were "lost" their data. After quick investigation i found out that MR creates data base at pathApplication Support/{name_of_target}/
. So I had to make merge and be sure that all users will be able to "return" their data back. Well, this is REALLY bad solution for that feature. Why did you choose that way? There are much better solutions like using bundle identifier. Of course it can be changed too, but this case is much rare then renaming of target. Or you can save it in the root of 'Application Support' folder. Or at least you can provide docs to your methods in Xcode with warning and explanation of how your methods is working.