I can't find my newly uploaded build in iTunesconnect when I click "Select Version to Test" for TestFlight.
When I tried to upload again, my Xcode shows:
But where to find my binary? And how to select the newly uploaded build for beta testing for TestFlight? Thanks.
Earlier I had the same issue and got an email from iTunesConnect pointing out some errors in the build I uploaded. It appears you have to address ALL the warnings (even though those are supposed to be OK for upload) before the build become visible in iTunesConnect.
In my case, I had warnings about alpha channels in my watch app icons.
For why can't you find your newly upload versions:
Check your email.And App Store review my send you an email for lack of user usage description.
Add the key and string value to Info.plist that App Store review ask.
And for why you can't upload your binary file again:
There is a 1.0.20 existed in iTune connect. So you need let your version +1. such as 1.0.21.
And every time you try to upload a new version, you must make your version greater than your latest version in iTune connect.
Then archive and upload it again.
Good luck!
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.
iTunes rejected the new version of my app. When I click to delete the rejected version I get the warning: "The app will be deleted from iTunes Connect and you won’t be able to use the app name or SKU again." How do I delete the rejected version without deleting the current version?
I guess you want to re-upload the new binary for review since it was rejected, right?
You do not have do that. In Xcode, simply upload a new binary and submit that one for review. You will be good to go.
Hope that helps :)
Downloading beta app from testflight app gives error at the end, says "Unable to download app at this time" on all my devices.
No error is in itune connect upload. App displayed and received notification on adding new app to testflight beta. But everytime same error.
This happened to me when I wasn't using the correct provisioning profile. Very frustrating error that doesn't provide any useful info, and leaves the previous installed version of your test build in a state where it cannot be launched. After I switched my provisioning profile to 'Automatic', bumped the build number, and submitted a new version to iTunes connect I was able to download the new build.
I'm seeing a similar error. I don't know for sure, but I suspect doing things in this order may have something to do with it (this seems to mirror what emrys57 is facing).
You have issued a previous TestFlight release (download/install was working).
You then submitted that version for formal review for publication in the App Store.
While the app submission is still under review, now you uploaded a new TestFlight build with an updated version number (but did not resubmit for App Store review).
It could be that while the app is under review something prevents the download. I seem to recall reading about something like this in one of the guides, but I can't remember where off the top of my head. In my case, as an internal tester I even face the error "Unable to download app at this time", regardless of whether I already have a previous version with the same bundle ID already installed or if I don't have the app already installed (i.e., it's fully uninstalled). I wonder if an accepted App Store review will clear up the issue; it doesn't seem like a good idea to resubmit that latest build for further App Store review if the version previously submitted is what you actually want released.
In my case, for the general testing audience, I have a separate bundle ID that is exclusively for beta testing. And that version is never submitted for App Store review (the one that's slated for App Store review I only use for the purpose of smoketesting the upgrade process with internal testers). That bundle ID for beta had to go through the one-time full TestFlight external review for the initial TestFlight external beta testing. But I've been able to keep adding new versions to that beta-only bundle ID for subsequent TestFlight releases without an issue.
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'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.