OK, knowing that, you can build a new version with complete different components in the bundle that, if files of previous version does exist, the app then offers the user the option of using them.
As MainWindow is one of them, I have to modify the reference in ist of course. I have built a new version changing the name of the xib/nib files that have been localized. One of my apps shows that issue with MainWindow.xib and as there are some modifications in references and classes, the updated apps crash each time you try to run as it is using a obsolet object.
The system, obviously, will use the first one and only a fresh installation will show localizations for that file. For example, if a xib/nib file is localized to different languages for the new version, the updated bundle will include both versions: the one in the root folder and the other one in each localized folder. So, the final bundle IS NOT equal to the bundle of a fresh installation of the new version. When user install a new version, all the files in the bundle are downloaded and copied in the previous existing bundle, but OLD FILES OR COMPONENTS ARE NOT DELETED (or not all are deleted). And, very important, iTunes, AppStore and iOS have modified some upgrading and installing rules in last versions. Just now, I'm suffering issues and users crashes because of a behavior of iOS system that I can't figure before.
I have just discovered something about version upgrades and the App Store.
0 kommentar(er)
