ios - xCode changes do not appear after creating an Archive - ios

I just created an Archive and now I am trying to add more changes, but for some reason, when I run the emulator, the changes I make do not show up, and the old version of the app runs.
Also, my repository shows the changed files, but for some reason xCode compiles the previous versions of them.
Would anyone know why the predicament I am in might occur?
Thanks!

Did you change the bundle ID in anyway to make the archive? If you do this xcode will build the app and it will feel like its installing the new one but you're really only seeing a previous version.
You should delete all versions on your phone, do a clean and then run it again to try to fix this unless there is something else going on.

Related

Meteor App Can't Run on iOS Device (Mobile Configuration Issue)

I'm having trouble with my iOS build. Not sure what it is.
After running meteor run ios-device command. It launches Xcode, but the "build and run" button is greyed out.
And when i expand the device drop-down, my phone is listed as "ineligible device" and the simulators is not even shown there.
I suspect there's something wrong inside my mobile-config.js file. Because when i remove this file, it runs as expected (but with default settings).
Hope someone can help explain this. I'm very new to both Meteor and iOS. Sending my packages and platform files as well for reference.
I had this issue too. There were one of two things that fixed it:
1) Make sure your project is linked up to your the correct iOS dev team/account & its not set to "none":
2) I had this issue come back again, besides fixing up the above.
So I restarted the computer, logged in and out and deleted the folder over at .meteor/local/cordova-build and ran meteor run ios-device to rebuild it. This was related to the mobile-config file because I changed the name of my app after I ran it the first time. Clearing up the cordova build stuff forced it to rebuild and perhaps this is why it fixe it.
I also deleted the previous app installed on the device (before I renamed the project in mobile-config.js. I did this because I suspected it had trouble installing because of the naming changes.

Delphi-XE4 iOS uploading new releases somehow ignored

I have a very mysterious problem.
I am somehow not uploading my new app versions correctly even if everything it seemingly correct. I determine this by download the "new" versions and seeing nothing has changed.
1)
Before release I test my changes are included and working on device-debug + device-adhoc.
2)
I then build and deploy for app store. Before uploading my .ipa file into "Application Loader" I make sure the .ipa file has just been generated. I then select it and the upload/verification process goes find without errros and some days later I get a message new app has been released...
3)
I then uninstall my existing app (just to make sure) and download and install the new app version from appstore - it is still the same. This is driving me nuts. I think I have tried to eliminate potential places where I could have errored, but somehow somewhere something is going terrible wrong for me. This is a fairly recent new problem - never had it in the past.
I am hoping if somehow can think of ways I can diagnose at what steps this is going wrong... I know it must be me that have an error somewhere. I recognize when something looks like a "Doh!" thing, but I believe I have tried a varity of methods to pinpoint it.
I have also tried clear out out scratch/temp directory before building + deploying. However, I am still wondering. Could it be some cache/path setting somewhere that makes Delphi compile incorrect app executable only when doing release builds? (I have of course also long time ago deleted all old directory paths that could contain earlier builds, but still...)
I did not see that you have already tried it on a new buddy phone & it worked. So editing my answer.
Can you try to remove your device ID from the profile settings in developer page & give a try downloading it.
There may be problem in building & compiling with Delphi.
Here is a post that differentiates between the same.
Please do see the accepted answer for that question here.
Hope that helps. (I know you are really pissed off waiting for the whole long app approval process & annoyed seeing the same old version.)
I had a buddy try download the latest app version, and he successfully and ran the new version... So I now must assume it is somehow my iPhone that is strange. I remove all app instances (debug, old appstore download) - then download the new version from app store. After that, my iPhone shows the "new" text on the launch icon, but still launches an old version... somehow

Storyboard won't update in simulator

I have a working app in Xcode, however when I try to build and run it the simulator displays an older version of the storyboard I was working on. I had changed some of the design on the storyboard but this does not reflect in the simulator, nothing is updated.
Does anyone have any ideas?
Delete the App on the simulator.
Clean
List item
Build & Run
Use NSLog(#"") in your controller to check code execution.
I just spent at least 6 hours on this. I have a solution, but I also submitted a technical support ticket to apple to try to get more info on the cause and proper solution.
Simply remove the references to your storyboard files and add them back in the same file group.
This seems to include the storyboard files back into the app bundle generated during build(which can be seen in the
DerivedData/APPNAME/Build/Products/Debug-iphonesimultator/APPNAME.app
From here I can see my changes reflected from the storyboards as expected.
PS - Are you using localization at all? I was.
I lost 2 hours to this.
Solution was braindead simple: delete app, turn OFF the iPhone 5S (iOS 7.1.1), and turn it bavk on.
When you turn on localization,
xcode moves storyboard file in localization folder (ex. Base.lproj/name.storyboard). When you build and run project on simulator, xcode copy name.storyboard into "derivedData"/Base.lproj/name.storyboard, but previous, created before localization "derivedData"/name.storyboard still exists. In this case simulator uses the file which can be found easier, i.e simulator uses old file "derivedData"/name.storyboard to operate.
Solution: Just rename the storyboard file, in navigator and in targets/general.
This error happened to me for the first time when I had multiple copies of a project on my computer. For whatever reason, the fact that there were multiple copies were making it look as if the storyboard had not been updated between copies and in some cases the code was not updated. I thought I had forgotten to throw the right copy on my flash drive before going home, but it turned out it's an XCode error.
Delete any multiple copies using the same name, restart XCode and open your most recent copy. Extremely bizarre, but I will probably use BitBucket or GitHub from now on instead of throwing it on a flash drive.
Deleting
~/Library/Developer/Xcode/derivedData/
worked for me!
I just have the same problem after localizationMy solution is clicking Product, Clean build folder. Then it will be fine
The storyboard on the simulator was what it should have been. The storyboard on the device would not update. I had to delete the application from the iPhone and then re-run it on the device in order to get the Storyboard to update on the device. Fortunately for me it was only test data, but I was using Auto-Layout on one view and went back to manual. I think that's what caused the issue for me.
I find that removing and adding storyboard file back doesn't work in my case, also it has side effects like it will automatically add a main nib entry into App's plist file (which subsequently makes the App fails to launch in iPhone simulator).
I don't want to try to delete the application from the simulator since I have many files under the Document directory of the App.
At last I find another way that works well: simply delete the "/Users/$username/Library/Application Support/iPhone Simulator/7.1/Applications/$app/$yourapp.app" file. The files under Documents directory are untouched.
(I have localized my storyboard as well.)
I found this same thing happened with Xcode 6.1.1 if I happened to have copied a project; the new project run in the simulator was actually still reflecting the old, original project.
In my case the problem was with how the default area was set up for derived data (essentially the location where the binary files go for a build). Mine was set to legacy and the simulator was using the wrong project, even after a clean. The solution was to go to Preferences->Locations, press Advanced, and change the location from Legacy to Unique.
I get this too when using localized storyboards - Run in Xcode just refuses to install the latest version of the compiled storyboard. I think it is something to do with the way Run copies changed resources across to the device - it does it differently than other forms of on device app installation.
The quickest way to get past this without deleting the app and losing any data is to:
Generate an Archive build in Xcode
Export this for Adhoc deployment
Double-click on the generated IPA to add it to iTunes
From the device page in iTunes force an update to that app
In order for iTunes to see that you have a new version your app build number will need to be incremented (if you don't do that already), before generating the archive.
I find this method means you don't have to delete an app off the device, you're just forcing it to install the entire install package rather than a diff which is what I think Run is doing.
I'm not sure what causes this, if it is a localized resources bug or what, but this is still a problem in Xcode 7 for me.

On app release update - are the images kept or renewed?

When submitting a binary update, if I've replaced some images will they automatically be rolled out? Or does the app on release keep the old images? Assuming of course, that I've cleaned the app, and refreshed the build prior to compile. I'm guessing it probably does reset the files... But wanted to hear from someone else??
The old images are removed and replaced by the new ones. Don't forget to update the version of the app in the project setting's:
When Apps are updated the download the entire app all over again. So any changes you make to your submission to the App store will propagate to all users who update.
The Only thing you have to make sure of is to remove the image from the Project or at least the build target.

iPad2 device build does not update when I do a new build

I am having a consistent problem with multiple different apps that the build on the device does not update when I make code changes. Here's my set up:
OSX Lion
Xcode 4.1
iOS 4.3.5
I build, and then run, the app launches on the device but it still runs the last installed version. In order to get the build to update, I have to do the following...
Remove the app from the device (press and hold on the icon, and click the x)
Clean and then build in Xcode
At this point if I try and run the app does not run. Xcode log says the app has started and stopped. If I restart Xcode and run, then the app runs successfully and is the updated version
If I make a single line of code change I have to go through all the steps above to get the app to update. The project is very large so a clean build takes 2-3 minutes.
Any ideas?
Update
I found the solution, this is related to the use of static libraries. The following article helped me solve this:
Changing the source of a static library needs clean and build in xcode 4
and for general background this was very helpful too:
http://blog.carbonfive.com/2011/04/04/using-open-source-static-libraries-in-xcode-4/
Double check your provisioning files and targets. Be extra sure to check the App ID in your targets, and Bundle ID in info.plist. Did you change any of that info before you saw this problem? I've noticed strange behavior like what you mentioned when updating those specific pieces of data.
Command+Shift+K -- Clean. I have found that you have to do a manual clean every time now to ensure that the build updates correctly.
In the event that xCode does not run at all, you just have to restart xCode.

Resources