Xcode 5 crashes when exporting archive - crash

I'm trying to distribute my iOS app in OTA mode. It worked fine until now, but recently each time I try to export my archive, Xcode crashes.
I'm using OSX Mavericks and Xcode 5.0.2 (all are up to date).
Below is what I'm doing:
Product -> Archive
From the organizer -> Archives -> Distribute
Save for Enterprise or ad-hoc deployment -> Click Next
I select the provisioning profile (ad hoc profile) -> Click Export
Here the finder appears and Xcode crashes.
I tried to repair disk permissions and read the forums for about 3 hours, still crashing !
Any help would be greatly appreciated.
Best
Jerome

Go into the iOS developer centre and accept the new terms and conditions or licensing agreement.

I was having the same issue in both Xcode 6.0 & 6.1, I removed the account from Xcod Accounts & added it again, It worked like a charm

Related

Crash while running old project on iOS 11

I have code which was initially developed on Xcode 3.2. It was then later update to become compatible with ios 7. But now when I run that code with Xcode 9 GM, it run alright on any iOS 10.x device.
But crash on iOS 11 device with following error detail:
Plus: When i open this project with Xcode 9 GM, Xcode doesn't show iPhone X simulator.
I think you have some old static libraries. iOS 11 supports only 64-bit libraries.
And also you can check Deployment target of your app. Maybe it's too low (I think ios7 deployment target is not supported now).
I think your app is running on 32-bit
As a reminder, new iOS apps and updates submitted to the App Store must support 64-bit. Support for 32-bit apps is not available in iOS 11 and all 32-bit apps previously installed on a user’s device will not launch
64-bit Apps on iOS 11
I don't know what is you exact scenario but possibilities of crash with payload could be following. Hope anyone of below all will work for you.
Please Try Following.
Disable "Enable guard Malloc" from diagnostics.
OR
You Can do Following:
delete all certificates from keychain.
Quit xcode
Delete xcode derivedData and delete all provison profiles
Restart mechine
Download latest certifcates and provison profile from Member Center
Click on certifcate i will install in keychain access.your key chain access should like this
OR
if you are using custom framworks, you need to put it inside the Embedded Binaries section located in the Xcode project under the tab Target / General.

Xcode 8 will not download all profiles

I had xcode 7.3.1 installed and yesterday downloaded and installed the production release of xcode 8. I click download profiles in my account area and not all will download. I tried deleting all in Finder. I tried clicking the Download button individually.
How do I get all profiles to download?
I ended up regenerating all my provisioning profiles which has worked for me. Quite strange...I don't know why that changed anything.
edit: on further investigation this is still happening...sometimes all our provisioning profiles aren't even showing up in the list to download let alone some getting stuck.

Testing Mac App Store app on real device - How to export?

I have been developing Mac App Store and iOS apps for several years now. I don't event want to know how many hours, days or weeks (?) I spend by solving provisioning problems...
One of my Mac apps targets OS X 10.7+. While everything works fine in genereal, after the last update some users reported problems when using the app on 10.7. Other OS X version work fine.
In the past, I simply cloned the project from my developing computer (iMac) to my MacBook running the specific OS X version. I then opened the project in Xcode, ran it and check what the problem was. This is far to easy for Apple, since this not possible any more.
The project only compiles (due to several reasons) in Xcode 7+ only. Xcode 7 runs on 10.10+, thus testing on 10.7 is not possible.
I have been trying to build/export the app to test it on my MacBook the whole day without any success. The app simply does not start on 10.7 on my MacBook. Of course the MacBook is a registered devices, included in my provisioning profiles, etc.
This is my workflow:
Removed all App Store specific entitlements from the app in Xcode/Target/Capabilities
Created new wildcard certificates and provisioning profiles that does not include any App Store specific entitlements
Selected the new profiles in Xcode/Target/Build Settings/Code Signing
Run Product/Archive
In Organizer select the Archive and click on Export
Here I tried several different combination (signing, no signing, etc.). No matter if I choose Export a Developer-Signed Application or Export as a Mac Application the result is always the same.
When I copy the created App file to my MacBook und start it nothing happens. The icon flashes once and this is all. Only the Console gives I hint about the Problem:
killed com.mycompany.myapp because its use of the com.apple.developer.team-identifier entitlement is not allowed.
Great... As explained I removed all entitlement from the app and from the profiles. Where the hack does this entitlement come from and how do I get rid of it?
Is there no way to test the App with all its features (== all entitlement) on another device?
I should have answered my own question earlier. Back in January I was somehow able to get the app running on my other Mac. Now I had to solve the same problem and it took some time to dig out the correct solution again.
So, maybe this will help others to solve the same problem. At least it will help my future-me to remember what has to be done :-)
Archive the app just as you would prepare the app to be submitted to the App Store.
Switch to the Organizer and select the just created archive
Select Export... instead of Upload to App Store...
Select Export a Developer ID-signed Application(second option). DO NOT select Export a Development-signed Application (third option). Actually I have no idea what's the difference is, but only the first one works...)
Click Next and the Organzier will fetch provisioning information from your dev account. DO NOT select the fetched provisioning profile but select Use local signing assets from the dropdown box instead
Click Choose and Export in the next step.
Done
Good luck and happy app signing...

Error when uploading to iTunesConnect

I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?
I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.
You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA
Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.
Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.
I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.
I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.

How to test my app on ios 7 using Xcode 6 simulator

I'm trying to test my app with ios7 using Xcode 6's simulator but I can't find the option to change it. Currently it only loads ios8 while my deployment target is set to 7.
Also according to this message from Apple:
Starting February 1, 2015, new iOS apps uploaded to the App Store must include 64-bit support and be built with the iOS 8 SDK, included in Xcode 6 or later. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code.
Does this mean that new apps cannot run on ios7 anymore?
Thank you for your help.
First, Change Deployment Target to 7.You can change Deployment target from target under Deployment Info.
Go to Xcode Preferences, Select Downloads tab and download iOS7 Simulator.
Now go to Xcode, you can find iOS7 Simulator on target device list, if not than quit and restart Xcode.
Hope it will help.
The deployment target is the minimum version of iOS that your application will be expected to run on. It effects how your app is BUILT and not where you run it. You need to choose an iOS 7 device from the run destinations menu and then do a Build&Run to build, install, and run the app on the iOS 7 device.
If you don't have an iOS 7 simulator device in the run destinations menu, go download the iOS 7 runtime from Xcode -> Preferences -> Downloads
Yes you can, go to xcode(7) preferences>select Components here you can download Simulater and Documents also.