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.
Related
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.
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.
I am trying to upload an app through the xcode 4 archive organizer. Whenever I try to validate or submit I enter in my itunes connect credentials but on the next window it asks for an application record and I get "No Value".
I have an app that is "waiting for upload" on itunes connect and I've made sure my login information is correct. I have no idea what else to try. Please help!
Here is a link to the exact problem I am having on the apple developer forums: https://devforums.apple.com/thread/95610?tstart=0
No one has posted an answer there either. =/
Edit: I ended up downloading application loader and doing it the old fashion xcode3 way and it worked just fine. I don't know why it stopped working in xcode4.
Sounds a bit strange, I have 10 apps in the iTunes store. We are going to need some more information? If it says "prepare for upload" then you still have to login to iTunes Connect and navigate to that screen. You will notice that on the top right of this screen you should see a blue blue button saying "ready to upload binary". Click that unless you have already. But I suspect you have missed this step?
Hmmm, I just did that for one of my apps and then is says "waiting for upload" ok. Not sure now. In xCode have you got all you provisioning profiles installed and the iTunes WWDC (or what ever it is called) certificate installed?
Are you using XCode 4.2? You cannot submit to the app store with it; you must use 4.1 (on Lion) or 4.0.
We were having the same problem and were using Xcode 4.2. We solved the problem by removing Xcode completely, moving everything in the Developer folder into the trash. Then we downloaded and installed the latest build of Xcode 4.2 via the Mac App Store. The problem was probably due to using an earlier build of Xcode or inconsistencies in Xcode from having upgraded from earlier versions over the years.
I had a project initially created in XCode 3 and used it successfully in XCode 4 Developer Preview version.
After upgrading to XCode 4 release, any time I try to run the project on the device, I get a "Argument Invalid" dialog. Except it doesn't tell me what argument.
How does one figure out what is wrong and why I can't run the app on my device any more?
Base SDK is set to 4.3
Deployment target set to: iOS 4.2
Ok, I have just managed to sort this out as I was having the same issue. This may not help you, but for me it was because I had a symlink inside a folder included in the project. I've removed this, and now it all works fine. Interestingly it works fine on the simulator in this case.
I've filed a bug with Apple on the issue (#9168893).
Just clean your producto
Menu>Product>Clean (Shift+Cmd+K)
I got the following message argument is invalid in response to some kind of USB weirdness. Sometimes it goes away if I unplug and replug the device, but what turns out to fix it more reliably is to start up iTunes. Usually, when I do this, the problematic device doesn't appear in the DEVICES list at first, but does after a few seconds, and once it does, the device and Xcode get along fine.
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.