Xcode crashes when refreshing provisioning profiles - objective-c

Last week I posted a question here where I explained why my Xcode is crashing when I press the refresh button. This question however got closed for being off topic but I dont really get why. (Stackoverflow should provide more information on this subject)
But I still got this problem and I cant get my app running with push notification because I think I'm using old provisioning profiles and I CANT refresh them without Xcode crashing!
I've created multiple apps with push notifications so I know the procedure but keep getting the error:
did Fail To Register For Remote Notifications With Error: Error Domain=NSCocoaErrorDomain Code=3000 "no valid 'aps-environment' entitlement string found for application" UserInfo=0x2340a0 {NSLocalizedDescription=no valid 'aps-environment' entitlement string found for application}
Does anybody know why my Xcode is crashing and how I can fix this?
Thanks.
And please post a comment if you're thinking of closing this question so I know why this question is closed.

Ravi is right. Here's Apple's official workaround:
Run /Applications/Utilities/Terminal.app and execute the following statement:
mkdir ~/Library/Developer/Xcode/OldPortalDBs; mv ~/Library/Developer/Xcode/connect1.apple.com* ~/Library/Developer/Xcode/OldPortalDBs
See: Xcode 4.6.1 crashing while interacting with the developer portal

It works for me if I removed this file "~/Library/Developer/Xcode/connect1.apple.com 4.6.1.db" before running XCode 4.6.1.

After some restarts and project cleans (and manually download!) it suddenly worked with push notifications. Xcode still crashes on refreshing and bug is reported.

Related

Xcode 8 Archive Error with Apple

I have a project I updated using Xcode 8 and Swift 3. It runs fine and I'm ready to submit to Apple. I complete the Archive process and then click 'Validate' in Organizer. After a while it gave me the following error, twice:
I tried to search online for this error and can't find anything. Why am I getting this error? I've agreed to all the Terms and Conditions set by Apple in the iTunes Connect side of things. All of my certificates and Profiles are Active too. Is Apple just having issues right now? I've seen others get around this issue with using the Application Uploader.
It's not a fix but I did as others suggested in the past and uploaded the .ipa file to Apple using the Application Loader that is in Xcode already. Worked and received confirmation it reached Apple.

TestFlight. Upload build issue

I'm the only one stupid? Since yesterday evening I am trying to upload to TestFlight my project and see ...
Dear XXXXXX, While processing your iOS app, XXXXXX 1.0(2685), errors
occurred in the app thinning process, and your app couldn’t be
thinned. If your app contains bitcode, bitcode processing may have
failed. Because of these errors, this build of your app will not be
able to be submitted for review or placed on the App Store. For
information that may help resolve this issue, see Tech Note 2432.
Regards, The App Store team
iOS 10 problems ?
but validation is successful
bit code = off, privacy keys -> set & Two days ago it was Ok, project code is not changed
Thanks in advance for answers

Getting strange error on iTunes Connect - ITC.halliday.error.unavailble with Xcode 6 iOS 8.1SDK

I'm trying to upload a new build via Xcode 6 to iTunes Connect release, and see a few errors, which might be related.
The build validates successfully, but when I try to submit I get this error:
When I check out the Prelease section on iTunes Connect, i see this strange error "ITC.halliday.error.unavailble"
Are these related? Thanks for the help.
UPDATE:
Apple seems to have fixed something on their end. I was just able to submit successfully. The "ITC.halliday.error.unavailble" message disappeared.

Why am I getting ab ITMS-4238 "Redundant Binary Upload" error when submitting to the App Store?

I'm on Xcode 6, and I'm trying to submit an iOS (target: iOS 8) app to the App Store, and I'm getting an ITMS-4238 error. It says there is already the same build already, but I've never successfully submitted this app so far. So there is no submitted build in iTunes Connect, so I don't know why I'm getting this.
What I'm doing is following:
Create an Archive
Submit binary from Organizer
I also tried to submit with ApplicationLoader but the result was same.
This is the error I'm getting:
Archive submission failed with errors:
Archive submission failed due to the issues listed below:
ERROR ITMS-4238: "Redundant Binary Upload. There already exists a binary upload with build version '1.0' for train '1.0'" at SoftwareAssets/PreReleaseSoftwareAsset
Here's a screenshot of the error:
Any ideas how to fix this?
Progress:
I solved my problem by myself.
I increased my build number from 1.0 to 1.0.2.1 .
I don't know why iTunes Connect thinks there is already binary version 1.0.
Try to increase the build number and submit the app. The version number can remain same. It worked for me :-)
You can also use ApplicationLoader. That worked for me.
In the info.plist in Xcode set your app version to the correct version in iTunes Connect. This worked for me to help update my app's version.

Application Loader Error: Launch Path Not Accessible

I'm trying to submit an application to Apple but am coming up with an error in Application Launcher.
Once I choose the zip file I hit Send and it comes up with the error:
Exception while validating: launch path not accessible
No idea what to do here, can't find much info on it at all on the net.
I have tried reapplying my provisioning / distribution profiles with no luck. Have re-opened XCode many times in case it was confused.
I submitted the same app a week and a bit ago and it went through fine, it got rejected so I made a few small changes and now this error comes up - no big changes were made.
The only thing I can think of is that I needed to update XCode and the SDK - from xcode_3.2.4_and_ios_sdk_4.1 to xcode_3.2.5_and_ios_sdk_4.2_final as the iPad I am using was updated to 4.2.
Any ideas on where to go from here would be greatly appreciated.
i had same problem, closed App Loader, restarted App Loader, problem solved.