I've been trying to upload a new build to iTunes Connect to update an app. I first used xCode 6 but got a email from Apple stating this:
Dear Developer,
We have discovered one or more issues with your recent delivery for "App". To process your delivery, the following issues must be corrected:
Invalid Swift Support - The files libswiftDarwin.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftUIKit.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftCoreAudio.dylib, libswiftFoundation.dylib, libswiftXCTest.dylib, libswiftCoreImage.dylib, libswiftObjectiveC.dylib aren’t at the expected location /Payload/App.app/Frameworks.
Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.
Once these issues have been corrected, you can then redeliver the corrected binary.
I thought it was a simple fix, so I just updated to the latest GM (Xcode 7.2) & completed the Swift 2 migration, however I received the same email. Could someone explain how to solve this and what those files are? This isn't a "files don't match" problem as seen in other questions.
I stumbled upon this as I've encountered the same problem. It's the first time I've been tasked with handling the release of a Swift app to the App Store.
I found that this answer by TALAA works a treat: https://stackoverflow.com/a/26949219/1567836
There is an "Embedded Content Contains Swift Code" flag in the Build Settings that needs to be set to YES. After setting this, clean the project before building again.
After the clean, you'll have to recreate a build to upload to the App Store. You might find that the new upload will get rejected claiming that a binary already exists for that number. If you update the build number (has to be larger than the previous one) then the new upload will be accepted.
As per the #Thomas You need to enable that flag and after that for the "Invalid Swift Support", I had the issues with Application Loader since Xcode 6.4. So, I started uploading the app from the "Organizer" (Xcode > Window > Organizer > Upload to App Store).
This solves the problem.
Inspect the payload and also the SwiftSupport folder in the .ipa file (by converting it to a .zip) and make sure the libraries in the email match across both those directories. Those need to match apparently.
You should probably not have libswiftXCTest.dylib in the Payload/App.app/Frameworks or SwiftSupport folders in something you're submitting to Apple. If you do, check the build section of the scheme for your App target and make sure you aren't including any test targets in your Archive step.
Related
I am uploading build to release app using Xcode 9.2 built with iOS 11 SDK. Binary is archived and uploaded successfully, but I get the following email back.
Dear developer,
We have discovered one or more issues with your recent delivery for
"". To process your delivery, the following issues must be corrected:
Missing Info.plist value - A value for the Info.plist key
CFBundleIconName is missing in the bundle ''. Apps that provide icons
in the asset catalog must also provide this Info.plist key. For more
information see
http://help.apple.com/xcode/mac/current/#/dev10510b1f7. Once these
issues have been corrected, you can then redeliver the corrected
binary.
Regards,
The App Store team
I found a solution.
Missing CFBundleIconName in Xcode9 iOS11 app release
But i need little bit more. I don't want to use *.xcassets file for app icon. I want to use image in xCode project folder for app icon.
Is it possible in xCode 9.2? if yes then how?
Haven't seen this listed on any of the other posts but this was my issue.
Make sure to check the target membership of your assets directory! If you do not correctly link the membership here, you will get this same super-generic error(Apple should do something about the error messages).
The target membership should correlate directly to targets for which you are using the icons. For example, I use this single directory for both my main app, and watch app assets, you must specify this by selecting the appropriate member.
There is a direct option not to use app icon from Assets
I am trying to submit my app into the app store but I am getting an error message from Apple:
Dear developer,
We have discovered one or more issues with your recent delivery for
"My App". To process your delivery, the following issues must be
corrected:
Invalid Bundle - One or more dynamic libraries that are referenced by
your app are not present in the dylib search path.
Once these issues have been corrected, you can then redeliver the
corrected binary.
Regards,
The App Store team
I tried using this answer to find out what's wrong but I am still stuck. I exported the iPA file of the app and used the otool -L MyApp command to find the frameworks. Here are the results:
These are my frameworks from the iPA file:
I downloaded all my frameworks using carthage and I added the frameworks to the embedded frameworks section:
However when I submit the app I get the same email back from Apple.
Thanks!
Not sure if this helps, but I encountered the same error once when updating an app. In that case, the problem was caused by a third party library that had to be updated to match the current set of architectures and SDK.
My suggestion is open your archieve from organizer > see product folder > open project.app > see there should no any .exe file(any where within folders as well).
I finally got it accepted by switching "Always Embed Swift Standard Libraries" to yes:
I have created a StickerExtensionPack. Apparently, Apple is treating a sticker extension pack as just another app that needs to go in the Sticker Category, fair enough.
However, when I uploaded the binary, I was sent back an email saying that the binary is invalid, because of the following reason:
Invalid Messages Application Support - The MessagesApplicationSupport
folder is missing and you have LSApplicationLaunchProhibited set to
true in your Info.plist. Either rebuild your application using the
current public (GM) version of Xcode or remove the
LSApplicationLaunchProhibited key from your Info.plist and resubmit
your application. Invalid iMessage App - The bundle contains an
invalid implementation of iMessage support. Add
MessagesApplicationSupport/MessagesApplicationStub next to your
Payload directory in your IPA.
MessagesApplicationSupport/MessagesApplicationStub must match the
binary at TapTeach.app/TapTeach and have no post processing applied to
it.
I'm doing a simple sticker pack. I'm on XCode and can not find LSApplicationLaunchProhibited anywhere in the info.plist within the my files!
Any guidelines on how to resolve this will be helpful. Thanks.
Try these steps:
turn off Bitcode from "Yes" to "No"
Change the version to CURRENT_PROJECT_VERSION = 1.10.11.
You don't need to recreate your project, just change the version. I reran the build and it's currently "in review" in iTunes without any errors.
So far, the only way I have been able to work around this issue is to repeatedly delete and recreate the project until iTunes Connect accepts a build. And really, I'm not even sure if the project recreation is actually helping - it could be entirely random - as it still only works about 50% of the time and turning off Bitcode, as mentioned by the OP, did not help.
At least two out of the three sticker packs I am currently working on have had this problem (with Xcode 8.0 and 8.1), so it's befuddling how this cannot be more widespread. I have to assume it's something specific that's causing it, but I am not sure what. So I guess until a proper solution is found: try, try again.
I try to publish on AppStore an App that contains Swift 2.0 files, but I receive the following email:
Dear developer,
We have discovered one or more issues with your recent delivery for
"EMO MILANO". To process your delivery, the following issues must be
corrected:
Invalid Swift Support - The SwiftSupport folder is missing. Rebuild
your app using the current public (GM) version of Xcode and resubmit
it.
Once these issues have been corrected, you can then redeliver the
corrected binary.
Regards,
The App Store team
I read the following thread oh stackoverflow (Invalid Binary Or Invalid Swift Support Invalid Swift Support / invalid implementation of swift) but I don't find any solution.
I Have a project that has multiple target and uses Cocoa pods.
This is a screenshot of the project navigator:
Ideas?
To be safe, all components of your app should be built with the same version of Xcode and the Swift compiler to ensure that they work together.
I think you need to do a pod clean and install. I reckon one of your swift pods was created on a old version of Xcode, you updated Xcode and then tried to do a submission to the app store.
Read the apple swift blog about binary compatibility and frameworks
You will also want to specify that your embedded content contains swift in the build settings:
EMBEDDED_CONTENT_CONTAINS_SWIFT
Enable this setting to indicate that content embedded in a target's product contains Swift code, so that the standard Swift libraries can be included in the product.
I just resolved an instance of this problem with Apple support.
The problem turned out to be some junk files were being included in the IPA file from my CI/CD system. In particular I had a .gitkeep file which came from a rsync command, and a .DS_Store file which I put there indirectly by poking around with Finder.
The fix was to tighten the rsync command I was using to import some frameworks from Jenkins to exclude .gitkeep, .DS_Store and any other dot-files.
YMMV. The support engineer agreed that it was a confusing error message.
My project on Swift 2.0 for iOS 9, (Xcode build 7A220) and I try upload the build to iTunesConnect for TestFlight, but a few minutes after uploading I receive an email:
Invalid Swift Support - The files libswiftCoreAudio.dylib,
libswiftCoreMedia.dylib, libswiftAVFoundation.dylib don’t match
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftAVFoundation.dylib. Make sure
the files are correct, rebuild your app, and resubmit it. Don’t apply
post-processing to
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftAVFoundation.dylib. Once these
issues have been corrected, you can then redeliver the corrected
binary.
What that means? Please help.
Do you use CocoaPods?
The problem might come from it if you are using Swift pods. To fix it you can edit Pods/Target Support Files/Pods/Pods-frameworks.sh and commenting the block after
# Embed linked Swift runtime libraries
More info:
Issue : github.com/CocoaPods/CocoaPods/issues/4188
I have faced this problem. My project was in objective C but when I submitted app to App store through Xcode 7 after successful submission of App, Build was in processing mode and I got email from iTunes that "Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it."
Solution: In Build setting of your Target Change Embedded Content Contains Swift Code to NO
After this when I submitted Build it get proceed with in 15 minutes. Hope This will help to someone