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.
Related
The title of this question basically says it all. I enabled Crashlytics in my Today extension, and for some reasons, the dSYMs are not being uploaded, even though I'm not using Bitcode.
I tried uploading them manually (from ~/Library/Developer/Xcode/Derived Data/Timelines-evxmjnxmpmcivkavmpijzakaxkrp/Build/Products/Debug-iphoneos/Timelines.app.dSYM), but the web interface doesn't really give me any feedback. It shows this screen:
No matter how long I wait, once I refresh the page, it goes back to the 'upload dSYMS' screen.
I think the problem might be that the UUIDs of the missing dSYMs don't really match those that I found locally.
Some notes on my setup:
Xcode 8.2
Today extension running on iOS 10.2
Bitcode is not enabled.
Fabric and Crashlytics integration was done using CocoaPods.
Archive wasn't uploaded to App Store. I'm just testing it locally on my devices. But since the entry for crash reports was created in the web interface, I assume the automatic upload should work anyway.
My question basically is: how exactly can I upload the dSYMs manually? And, second one: how can I make the automatic upload of dSYMs work? Thank you.
It is described here completely ==> fabric.io.
As it said you can download it from activity tab in itunesconnect and then upload it to crashlytics website.
Although I can upload successfully new versions of my app to iTunes Connect, I can't see them nor the previous ones under the "Prerelease" section in the app's page. Instead, I get a message saying "Upload your builds with Xcode 5.1.1 or later, or with Application Loader 3.0 or later". In the "Versions" tab, under "Builds", when I press the "+" button, I get an error saying my request couldn't be processed. Am I missing some needed configuration?
It looks like this is an issue with iTunes Connect, not something you did. There are a bunch of tweets right now of others experiencing the same issue.
What you'll see right now if you look at the itunesconnect hastag on Twitter:
Our list of pre releases in #itunesconnect disappeared for no
reason... /cc #APPLEOFFIClAL 0 retweets 0 favorites 38m ago
Weird…all of my app builds have disappeared from iTunes Connect
itunesconnect 1h ago
itunesconnect: (slow / misbehavin') for everyone or just me (dot tumblr dot com) 2hours ago
itunesconnect - no earlier uploaded binaries are seen in any application. Seems like a bug. Fix it Apple, I have to deliver to customers.
Unfortunately, the official system status says everything is green. It's not clear how you're supposed to report an issue.
Indeed it was an apple bug. After two hours, the prerelease builds appeared again.
I am trying to upload my mac xcode project on mac app store, but each-time it shows invalid binary status. I have checked many answers in stack overflow as well. But issue is not resolved. That's why I am posting new question here
I tried some options -
1.. Removed all warnings
2.. Checked by quiting xcode, cleaned container folder
3.. provisioning profile is valid, and matching to the bundle id. I checked by deleting all certificates and provisioning and install required ones again.
4.. Created new provisioning profile and certificate 3 times. But same issue
5.. uploaded 3 times directly through xcode 5.1.1, and 2 times by Application Loader. But showing Invalid binary for all.
6.. App is properly sandboxed with proper permissions
Any idea. Thanks in advance.
Invalid Binary
When you get this error, apple will send you a mail with reason. In my case this was the email:
Dear developer,
We have discovered one or more issues with your recent delivery for
"App-Name". To process your delivery, the following issues must be
corrected:
App sandbox not enabled - The following executables must include the
"com.apple.security.app-sandbox" entitlement with a Boolean value of
true in the entitlements property list. Refer to the App Sandbox page
for more information on sandboxing your app.
App-name Mac.app/Contents/MacOS/app-name
Once these issues have been corrected, you can then redeliver the
corrected binary.
Regards,
The App Store team
Also, you shouldn't be using XCode 5.1.1 itunes connect has changed a lot now.
Please update to 6.0.1 or use the new beta version 6.1
Xcode 6.1 GM seed for OS X Yosemite
hope this helps
I've installed Testflight (1.2 B3) as stated in the documentation. Builds are uploading and updating fine. I can see sessions (mostly anonymous :/), I receive the logs (TFLog) - but I do not receive any crash reports. I even introduced a crash-on-event (a method not found thing) - but theres is nothing on Testflight about it.
Provisioning is via a developer profile which embeds several devices.
The problem occurs on iOS6 and iOS5 / iPhone5 and iPad3. The is being build against iOS6.
Any ideas?
UPDATE
I've tested several other frameworks and ways to receive crash reports. Nothing worked so I suspect something in my code (obviously). Are there any other switches that XCode 4.5.1 might have enabled and that way disable any error reporting during a "production environment" like setup?
UPDATE 2
As of now we're using Testflight only for distribution of beta versions and switched to Crashlytics for crash reporting. It's a bit more streamlined and fetches most crashes.
I also do not get any crash reports via TestFlight. This is what the TestFlight people told me:
Our team is currently looking into an issue associated with auto
versioning of the app when uploaded and SDK data not reporting
properly. Looking at the URL you provided it looks like the build
version is not changing before uploading the app to TestFlight and our
auto versioning implementation is causing an issue with general SDK
data reporting.
I will share this with our team and we will contact you when we have
an update available.
I tried to update the build version to avoid auto-versioning, but it did not help me. But maybe this issue is hitting someone else.
Testflight did not satisfy our needs to log crashes. That is why we skipped to Crashlytics (as I said in the original post). The issues with Testflight seem not to be resolved. We still do use it for distribution, that is what it's good at.
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.