I've seen a few other SO questions that are related to this; but I've been through all of the fixes with no joy.
My company had one Mac for use for the team. This worked absolutely fine. We really needed another so we have another. I exported the developer profile from the first Mac on to the second Mac. This seemed to work fine, we can test on local devices, etc. However, now we cannot upload on to the App Store from either Mac- they just get stuck on authentication with no error.
Things I've done:
Tried a different connection
Set the HTTPS proxy port to 80
Run the application loader and XCode at the same time
Regenerate our certificates and provisioning profiles
Set the build settings to various combinations of certificates and profiles
Turn it off and on again (more than once)
Update Java
Bump version and build numbers
Checked the licence agreement (no updates)
Deleted the XCode DerivedData caches
I can access the Apple developer sites just fine- developer.apple.com, the iTunes Connect stuff, all of that without trouble.
Some answers on StackOverflow suggested that we wait for some more time and be patient, others stated that restarting OR reinstalling Xcode should do the trick, but none worked for me. However, updating iTMSTransporter (Apple's command-line tool) worked for me, and if none of the above worked for you, I believe this one should ...
Simply create a back-up for the existing installation / folders, This is important because during the (new) install your previous installations will be removed by Transporter:
cd ~
mv .itmstransporter/ .old_itmstransporter/
Now run the following command to update Transporter:
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Hope this helps somebody.
I solved this problem by erasing the private data using the builtin tool (Window -> Projects) and then deleting XCode itself and reinstalling.
Had the same problem, after update to xCode 7.0.1.
In my case, cleaning project DerivedData and reboot Mac OS fixed it.
Related
Just switched to a new MacBook after my old one got a logic board issue and died. I transferred some apps over from an external hard drive, and none of them will run-- I just get the error in the title.
This has been addressed before, but none of the solutions have worked. I've tried:
Manually setting file permissions
Cleaning the project multiple times
Setting the compiler for C/C++/Obj C to default
Restarting my computer
Replacing my info.plist file with a clean one
Deleting derived data
Checked my architecture settings are accurate
Some other solutions I've found on here (deleting folders that code was moved into, etc) aren't applicable
Worth noting that in addition to switching computers I upgraded Xcode to the latest version (my version on the previous computer was about a year old).
Does anyone have any other thoughts? I'm stuck and have no idea what else to try.
Try change permissions recursively. Go to terminal, open folder with your project and write:
sudo chown -R $USER .
I realise that there are a few questions/answers and I also realise that I can download via the developer page, however it says 7.3 is installed ...
but when you start Xcode it is still the previous version.
Is there a work around or do you have to download a fresh copy? With a very slow connection I would rather avoid it.
Sadly you are going to have to download a fresh copy of Xcode. Same thing happened to me and I tried everything. Restarting my computer, closing it in Force quit applications and tons more and nothing worked. Fresh install would be the only option for you.
Check that you don't have any backup drives/clones/time machines etc connected, and that you only have the one MAS Xcode version installed (you can check if it's a MAS version by going to /Applications or wherever, and opening the Xcode folder with Show Package Contents, then looking in the Contents folder for a _MASReceipt folder. If that's there, it's a MAS version).
The MAS app has an issue where it will update the app on backup drives etc that are connected to your machine when you do the update, often before it updates the version you expect it to update (in /Applications). This could mean it may need to do a few updates before it gets to the one you're actually using.
If you like to keep old versions of Xcode around, always delete the _MASReceipt folder from the old ones. That will prevent the MAS app from upgrading them later.
I recently transferred my MacOS continuous integration server from a MacBook Air to a MacMini (using Migration Assistant) and while all my settings seemed to carry over fine, whenever I run one of my Bots, I gets errors about missing certificates. I've tried everything (adding self-signed certificates, etc.) but to no avail. I even tried deleting the Server app and reinstalling it from the AppStore but that still didn't help. What else can I try?
Alright, after many days, I finally figured it out. First, I wouldn't have had any issues if I had just done a clean install on my MacMini but hindsight is 20/20. The solution was to rm -rf the /Library/Server directory (you'll need to sudo su before you do this). That directory contains all the settings for the MacOS Server and it remains even after deleting Server.app. By deleting Server.app, deleting this directory, and then installing Server.app again, you force Server.app to properly regen all the proper certs, etc.
Yes, you'll have to recreate your Bots and repo links but at least it will all work!
I have a Mac app I have written to support iCloud. However, I get this when trying to run the app:
error: failed to launch /Users/padsoftware/Library/Developer/Xcode/DerivedData/Scrawl-heofvoywsunchdhjowxkvkoiqvan/Build/Products/Release/Scrawl.app/Contents/MacOS/Scrawl
The odd thing is that this appears for all of my Mac apps, with or without iCloud, with or without sandboxing, with or without entitlements, or ever with or without code signing. Any idea on how to fix this?
I had this problem too. For me, it was a code sign issue. Make sure you're signing with developer, not distribution.
I encounter this problem every once in a while. Like the others mentioned, these are the steps I take:
1. Clean (Shift+Cmd+K) ------
Removes all the product files, as well as any object files (.o files) or other intermediate files created during the build process (Apple Doc)
2. Navigate to "~/Library/Developer/Xcode/DerivedData", delete folder for app in question ------
Derived data consists of project indexes, logs, and build products including intermediate files (Apple Doc)
3. Restart Xcode
One or the other usually fixes it. I haven't had to change Code Signing settings, but that would be my next step. Wouldn't re-install Xcode unless absolutely necessary.
I had such problem also and restarting Xcode Fixed the issue .
even it happened after renaming the application ....
Under Build Settings make sure you are signing with a valid developer profile for debug and release.
Then Build for Testing
That fixed the problem.
"Product"->"Scheme"->"New Scheme" fixed my problem
Just in case it helps anyone else, my problem was fixed by rebooting my iPhone (4S). Then the app suddenly appeared on the Springboard (it was like it was already installed but somehow hidden).
...I did all the other steps (restart Xcode, clean project, delete derived data) but none of it worked this time.
What worked for me... I was already code signed as developer so I cleaned my code
menu bar -> Product -> Clean
That still didn't fix it but I noticed that I was getting handshake error, I had a large amount of apps already running on my phone (~15-20) so I exited out of all of them and retried. It worked after exiting out of all other apps.
For one of my clients, I've developed a small iOS app. I'm a member of their dev team, so I've been using a development certificate to sign my local test builds.
Now the app is almost done and it should go into internal testing on the clients side. I created an archived build of the app which I then sent to my client. They imported it into the organizer and tried to "Share" it to be able to re-sign it using an ad hoc profile.
Creating the .ipa fails with an "no such file or directory" error though. The archive appears to be fine otherwise - the organizer shows all the usual information, the icon, and it will let them export it as another archive. Creating an .ipa without re-signing fails as well, which leads me to believe this is not an issue with ther certs and provisioning profile.
If I try the same thing on my side, writing an .ipa from the very same archive using my development cert, the operation succeeds.
It may be worth mentioning that the same procedure was working fine while we were still using XCode 3.x on earlier projects. This is the first time we've been trying this using XCode 4.
No additional (static) libraries have been used.
Any help greatly appreciated!!
Edit:
Someone at the apple dev forums suggested to me that I should check the system console for xcode error messages while attempting to export the .ipa - none were printed out. We discovered some other, older messages however, which read as follows:
18.04.11 13:54:35 /Developer/Applications/Xcode.app/Contents/MacOS/Xcode[123] /Users/User/Library/Developer/Xcode/Archives/2011-04-15/Foobar.xcarchive/dSYMs/Foobar.app.dSYM/Contents/Info.plist:
set flags (was: 00200000): Operation
not permitted
The timestamp is roughly at the time when my client first imported my archive, but we can't be sure since we didn't watch the console back then.
The message had been printed multiple time, once for every single ressource file contained in the bundle. Does this tell you guys something?
Problem solved.
Following another suggestion on the apple dev forum, we repaired permissions on both systems. Additionally, I built and archived the app again and used a different way to transmit the archive to my client. We did all of this in one try, so I can't quite tell which of these measures actually did the trick. If you stumble across this because you have the same problem, you might want to try all of this, too.
Thanks for listening!
Update:
It happened again - and this time, we tried to solve it step by step. Result: It's all about how the file is being transmitted. I just attached the archive package to a mail to my client, that's what broke it, although I don't know why. Zipping the archive before transmitting it solved the problem, however.
After downloading XCode 4.3 beta with the IOS 5 SDK, the Organizer function to share and archive stopped working with a cryptic error "No such file or directory found".
It turns out that this is related to having two different versions of codesign_allocate . To fix the problem, do the following in a terminal window.
sudo ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin
Another hint - try the manual way to create a shared ipa - since it gives you a lot more detail of what went wrong. See http://blog.dmahajan.net
Can you see if this is also linked to your problem?
EasyCoder's answer fixed this issue for me - I have the 5.0 beta SDK and had the same problem.
I ran the following and it was fixed:
ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin/codesign_allocate