Hi I have the following problem.
I am almost finished with creating a new update for my app.
Now I wanted to try if when I install an old version of my app and then run the new version of this app via Xcode on my iPhone.
If the app gets updated correctly to the new version.
Unfortunately this is not the case. I ran into a few problems:
the icon does not get updated (only looses the shine cause the new
one does not have on)
at the start screen of the app there are still parts of the old
version visible like buttons and labels
most of the app gets updated to the new version correctly.
is this a bug or problem from Xcode or will this be the same when my customers update via Appstore?
This problem won't be there when your customer updates via Apple. I have seen problems like this only during debug.
Related
I have released the update of iOS app on iTunes. It is available on App store but neither it is showing in 'updates' tab nor it is updating automatically. Finally i uninstalled the old version and installed the new version from the app store.
This iOS app is developed in phonegap.
You should wait a few hours before a device finds the updated version of your approved application. The application update needs to be distributed to multiple servers dedicated to the App Store.
It is possible to manually check for updates on your device since iOS 11. Tap near the top of the screen near the ‘Updates’ text, then hold and pull down, then release.
Please note that you will not get the update automatically when you see a download button on your application page in the App Store. This means that the version on your device is signed with a different certificate than the released version in the App Store. Simply click on the download button to resolve this.
Hope this helps!
It's an open bug from apple side since last 5 years which is still yet to be fixed.
For reference kindly check their official site :
https://developer.apple.com/forums/thread/52767?page=3
I have been working on an iOS app update and am ready to submit it, however I am having a small issue I am concerned about. I create an ad-Hoc version for testing and when I try to synch the update over to my phone via iTunes it won't give me the 'update' option next to the app. The buttons in iTunes says 'remove'. iTunes actually forces me to first remove the old version of the app and only after it is removed, iTunes gives me the option to install the new version and then the app works fine. The only problem is that this is not really testing the update process and I am concerned that once I release the app to the app store my users will have the same issue where they will not be able to just update the app, they will have to remove the old app first and then install the new version. Any idea what might be going wrong here?
iOS takes care of updating Apps, as far as bundle identifier in your info-plist is the same, any newer version will show as an update in iOS. But in iTunes things work differently. You don't have to worry about these things.
If you want to test effects of updating an App, Install the old version from AppStore. Connect your device and Run the project from Xcode. Now this will work the same way as updating your app.
There is no problem from your part. Maybe this time iTunes is not smart enough to know that your ad-hoc version is an update one or maybe the version of the app on iTunes and on your phone is the same. I've made a lot of update to my apps, when you submit a new one to AppStore your user won't face this problem. They will find an update button for your app :).
We have submitted an update version of our existing applications in the App Store recently. But we have received a issue from one of the users, saying that the app is not functioning properly after the update. So in order to replicate the same, what are the steps to reproduce, so that i can analyse the issue?
Any help will be appreciated.
To simulate this before pushing yoru updated version to the AppStore you can:
Download the old version of your app from the appstore
Run the updated version of your app from XCode on the same device.
What will happen behind the scenes is that your app will be updated in a way similar to the Appstore. Your app will be partially updated while your doucments folder will stay the same. (what usually causes problems)
This solution is better because it lets you check for problems before and update was pushed to the Appstore.
Yeah, I get this a lot. The solution is a bit annoying, but you need to keep a history of IPAs you've submitted so you can put the on your phone through iTunes (so not the simulator) and then, run your code on your device putting a breakpoint on your applicationDidFinishLaunching handler in your app delegate, and start tracing from there. You should be able to find the old app store version in your organiser from the last time you submitted, or, go through your SVN/GIT history and checkout the version tagged to your release version.
Many times in the past that has happened to me where I test a new revision and everything looks fine but when I submit an update and is approved, users start complaining about a crash or lost data.
This is way I approach the problem.
(This is most important step) You need to either have your old code or old binary installed on your actual apple device. (Physical iPhone / iPad)
Now go to iTunes and install your new update.
Attach your physical iPhone / iPad to you computer, Launch Xcode and start debugging it.
NOTE: There have been many times when things work perfectly in the Simulator but break on the actual device. Its always important to test your code on the real thing as that is what the users are going to be on.
All that is required is to have the version of the app that is in the app store on your device, then install the updated version to your device. You can debug it using Xcode when you install the new version.
I have an app published in the store, which i want to change so much its internal working, that i decided to start over. I successfully finished the new version of my app, but when i install the previous version of the app, and run the new version from xcode to check if everything is compatible, i get "Could not change executable permissions on the application".
What i did was to change the bundle identifier of the new version of the app to match the old one, but i cant get it to run under the same name. Do I need to do something else? The app runs great if the old one isn't installed, but when I have the old one installed, and I want to run the new one, so it replaces the old one, i get the error i mentioned above.
Thanks
The problem I had was related with the use of unreleased iOS beta software. It is solved by testing my apps on a device running the last released OS (iOS 5.1.1 at the moment).
i think you should try to remove the app that have same bundle identifier in you iOS device ,
hope this can help you!
I just had this same issue which almost caused me a meltdown. I'm on xcode 5.1 and ios 6. My answer was to delete the app on my iPad by holding my figure over the app icon, then pressing the 'x' that appears next to it. Then I went back into xcode and built the project.
So I have this app that is already on the app store. To get support for multi language localization we recently changed the localization configuration.
Old configuration:
./Localizable.strings
New Configuration:
./Swedish.lproj/General.strings
./Swedish.lproj/Localizable.strings
./Swedish.lproj/Settings.strings
If I remove the old version and install the new one everything works as expected, but if I leave the old version on the phone when I install the new one, the translations in ./Swedish.lproj/Localizable.strings won't be visible. So it seems to me like the old ./Localizable.strings is still left on the phone, hiding the new ./Swedish.lproj/Localizable.strings. The translations in ./Swedish.lproj/General.strings and ./Swedish.lproj/Settings.strings both works.
My fear is that if we release the update as is the users would be forced to uninstall the app before installing the update to get the translations to work, which would mean that they lose all their saved data. So you can see why this issue has high priority.
If I have understood the cause of the problem correctly, my question is how do I get rid of the ./Localizable.strings already present on the phone? The more general question would be how do I solve this problem?
Are you testing this in debug mode and Xcode is installing the new binary onto the device/simulator or are you doing an Adhoc build-and-archive and then test the update via itunes?
I know that xcode at times will not overwrite files when doing an build and run in debug mode. A touch of the file will not help, but only a clean-all, exit and restart of both Xcode and simulator cures it.
If you are using the adhoc build then the complete app bundle sould be overwritten. If this is not working something serious is at fault.