I have an app on the Mac App Store which is at version 1.0.
Later, I upgraded to the Mountain Lion GM and the Xcode 4.4 GM.
I've added features to the app and I'm trying to submit it as version 1.2.
It passes validation and gets successfully submitted, but I keep getting "Invalid Binary" and "Invalid Signature" errors.
When I try
codesign -dvvv myapp.app
It successfully prints out the identifier, authorities, etc.
I'm completely lost because nothing has changed except for the code and the inclusion of sandboxing.
I ended up deleting all my profiles and certificates and re-downloading them.
Related
Issue Description
I'm working on an app based on ReactNative 0.40, I am using Fastlane for beta deployments and I'm using Match to manage my signing profiles. Most things work as expected, however:
Issue:
When I try to run my app on a physical device directly from Xcode 8, it gives me this error:
This is what I've tried:
[x] Follow Apple's Entitlements Troubleshooting Guide
[x] made sure that the entitlements selected in XCode's "Capabilities" screen match the ones selected in the app id on the developer panel.
[x] Re-ran match. i.e. fastlane match development fastlane match adhoc fastlane match appstore
[x] Ran fastlane match decrypt and then security cms -D -i /path/to/***.mobileprovision. Although I'm not entirely sure what I'm looking for that is missing/extra/invalid.
Questions:
What should these settings be for both the project and the target?
Which signing identity should be used for running the app on a device from xcode during development?
What else can I try to troubleshoot this?
... and, finally fixed this. Just in case some other poor soul out there is spinning their wheels, here's what was broken in my case.
The App ID on the dev portal has 3 options for data protection:
However, Xcode doesn't:
The setting has to match anyway, so I hadn't noticed that the entitlements file was set to NSFileProtectionComplete as opposed to NSFileProtectionCompleteUntilFirstUserAuthentication
Making that change, along with switching to Automatic Signing (which in hindsight might have had no effect), fixed the issue. I may switch back to match-managed development profiles and see what happens.
I got this error due to trying to build with a wrong Scheme.
I used Release config by mistake instead of debug config
So double check whether correct Scheme / Build config is selected
I am new to this Xcode and we are using 7.3 version. We had a problem in launching the app on iOS device with the Xcode after connecting my Mac to the iOS device (iPad).
I have connected my iPad to Mac and then build the solution but I have been encountered with an error message along with Fix issue button in the warning message.
If I clicked the Fix issue button then I am getting the error as:
Unable to fix code signing issue. Xcode failed to resolve the issue. Check your code signing settings, ensure you have a matching signing certificate and provisioning profile installed; and try again
Because of this error I could not be able to run the app on my iPad device. Can you provide me a solution on how to fix this issue and make the app run in my iPad device?
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.