I have been trying to submit my app multiple times to the app store and I keep seeing this error:
Invalid Swift Support - The files libswiftPassKit.dylib,
libswiftCoreAudio.dylib, libswiftContacts.dylib,
libswiftCoreLocation.dylib, libswiftCoreMedia.dylib,
libswiftCoreData.dylib, libswiftAVFoundation.dylib don’t match
/Payload/MyApp.app/Frameworks/libswiftPassKit.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftContacts.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreLocation.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreData.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/libswiftPassKit.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftContacts.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreLocation.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreData.dylib,
/Payload/MyApp.app/Frameworks/libswiftAVFoundation.dylib.
Is there something else i'm doing wrong? Or is it still not available? I'm not able to find any resources to help with the above
Seems like it's an issue with Cocoapods. As per below:
https://github.com/CocoaPods/CocoaPods/issues/4188
The current latest version of Cocoapods is 0.39 beta 4 which does NOT work.
You can check your
Build Settings -> Embedded Content Contains Swift Code.
If it's NO,you can set it to YES,and then have a try.If it's not working.You can update your Mac system to Mac OS X 10.10.5 and your Xcode to Xcode 7,just rebuild your project with iOS 9,and then Xcode will tell you which you must deal with.
Related
I created an app using expo cli. I also created the build for the same using expo server and was trying to upload the app to the app store.
However, the previous version of the same app was written in Swift and I get this error.
As a result Apple is rejecting my app.
I have maintained the same bundle Id of the app.
Error :
Dear Developer,
We identified one or more issues with a recent submission for App Store review for your app, "My App Name". Please correct the following issues, then upload again.
ITMS-90433: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have the correct code signature. Make sure you’re using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don’t just modify the code signature of libswiftAVFoundation.dylib.
Best regards,
The App Store Team
I don't think that this solution works because when the application is built on Expo, using the command EAS, is the expo server who creates the IPA, and in one step copy the file libswiftCore.dylib (in my case) and is signing it using "codesign", then making changes in the local Xcode I don't expect solve this problem. ¿Maybe making some change that allows the project tell expo which signature must use in the swift support file?
thanks
solved by changing ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to YES in my project configuration.
In XCode select your project -> Build Settings and look for "Always embed swift standard libraries". If NO is selected, switch to YES (for debug and release), and it's done.
It is recommended to clean your build in Xcode before building and submitting again, just to make sure you have no residues of your old build left!
Solution 2:
The other solution I came across is the version mix match. Make sure you are using correct version of expo. Otherwise just update it to the latest one.
I tried updating a stand alone WatchOS app to the App Store and got this message from iTunes after uploading it:
ITMS-90492: Invalid WatchKit Support - The file WK doesn’t have the correct code signature. Make sure you’re using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don’t just modify the code signature of WK.
I have uploaded previous version without a problem, so I think it might have something to do with using WKInterfaceDevice().play(.click) in my code which is new to the version uploaded, but I am not entirely sure, has anyone ran into a similar problem and how did you fix it?
This appears if you have XCode beta installed on your Mac. It doesn't have to run just its simple presence results in this artefact.
I am struggling to get my build uploaded to itunesconnect since upgrading to XCode8 - might have to do with the swift 3.0 syntax update?... i am new to iOS dev, having been doing it now since xcode 7.1....
I submit the through Organizer, the ipa uploads, but then i get an email from itunesconnect:
"Invalid Swift Support - The expected dylibs are missing from the app’s Framework location, such as /Payload/Health Storylines.app/Frameworks."
My app target uses obj-c, and the UItest target uses swift.
ive read: Invalid Swift Support / invalid implementation of swift
i cant find any embedded swift settings in xcode8...
ive read:Invalid Swift Support - Files don’t match
but in the .sh they want some lines commented out - it only runs on xcode version below 7...show this shouldnt matter.
ive just read http://radex.io/xcode7-xcode8/
there are some cocopoads code signing topics in here...not sure if this is relevant?
this the the contects of the .xarchive:
Im thinking swift need to be turned off somewhere, but dont know where...
Help much appreciated!
Seems like a problem that I had. Try archiving and exporting the IPA with XCode 7.x.x, and then upload it with Application Loader (XCode 8 GM). Also, what is your macOS version?
I had the same issue If you are using fastlane and swift 2.3 you may try adding toolchain "com.apple.dt.toolchain.Swift_2_3" on your Gymfile, it worked for me.
today my app update it has been released in the store, when updated or downloaded for the first time the app immediately crash on start.
I've tested the app on simulator and on device (the same where I've installed the update from the store) and I never experienced this problem.
My update it has been submitted with Organizer after the archiving, in the Distribute section.
Apple do not perform these types of controls before to release an app?
Anyone experienced a similar problem? I have no idea what could be the cause..
Thank you, Stefano.
Here's the best way to test a production build without deploying to the store:
Set your build Scheme to "iOS Device"
Do an Archive build
Select your archive and click Distribute
Choose "Save for Enterprise or Ad-Hoc Deployment"
Pick your code signing cert
After saving the ipa file, use Apple's iPhone Configuration Utility(*) to install it on your device
You should always perform two tests:
installing on a blank device after uninstalling your app *and any profiles in Settings -> General -> Profiles"
installing over the top of the previous version of your app, to make sure any files/preferences/etc are properly converted to the new format
(*) the iPhone Configuration Utility is mostly used for enterprise app deployment, but it's also useful for developers and is available as a free download for mac and windows at support.apple.com. You can also use iTunes instead, but it's convoluted.
As for why your app is crashing? No idea... it could be anything. Standard debugging advice applies.
The issue is related to the Framework. I had this exact error. It wasn't a case of logic as it was crashing before the AppDelegate was even called and my usage of NSMetadataQuery was much later in the life cycle than that.
It turns out that weak linking the Foundation framework was required.
Problem was solved by changing (under the Project Info in Xcode) the dependency option of the Foundation.framework from required to optional. Check for any such frameworks.
Try deleting any old versions of the app you have on your device, and reinstall. Also try on a different device, maybe with a different apple id to your developer account.
This happened to our app also, and apparently, other apps too.
Apple is aware of the problem and is currently working on a solution.
see this article:
http://techcrunch.com/2012/07/05/apple-responds-to-app-crashing-issues-has-a-dedicated-team-working-on-a-fix/
If you are using core data & you have updated database in your latest version without versioning core data in that case app crashes on launch after update.
I'm really newbie in iOS and I have to handle a complicated situation. I was given an iPhone app developed by someone and I have to make it work. The guy who developed it has told me that it worked, but sometimes crashed in an iPhone. I've never developed using iOS and I don't really know how this app works.
Well, when I open the app with Xcode, the first problem that I detect is some errors with the references. The app uses the project CorePlot-CocoaTouch.xcodeproj. I've added again this project and solved the references (I've followed some other posts like this one: http://www.jaysonjc.com/programming/pie-chart-drawing-in-iphone-using-core-plot-library.html).
I want to test it with the simulator (I don't have an iPhone yet). I have a doubt here...should I use iOS Device, or iOS Simulator as Base SDK? Firstly I chose iOS Simulator, but it appeared a problem with Cocoa.framework (it turned into red).
Anyway, using iOS Device as Base SDK, I build the project and it says "Build failed (59 errors, 3 warnings)". I check out the errors, and most of them are "Expected specifier-qualifier-list before ..."
Can anyone help me? This is more or less the situation, but I can provide more specific details if they're needed.
I'm sorry if I'm talking about something really basic, but I've been trying to solve it for 2 weeks and I give up. I've tried to talk to the guy, but he's not really helpful..
Thanks for the replies!
By the way, I didn't say it and I don't know if it's relevant or what it means. The guy has a directory called "Libraries" where it's stored the CorePlot. The files there are the same than if you download the CorePlot project from other source. The only exception is a folder called "SDKBuild", which contains files like "build.sh", "iphoneos-SDKSettings.plist" or "iphonesimulator-SDKSettings.plist". I'm really newbie, so it's probably obvious, but I have no idea...
just try to add CocoaTouch framework to your project.
and for base SDK use "latest iOS".
Right click on the project name in 'group & files' set on the left of xcode. Choose add -> Existing Frameworks.
Find Cocoa.framwork and click add. Do this to all red colored framework.
Choose IOS Simulator as base SDK.
Try run it..
If you want to run the app on simulator, you have to build with iOS simulator. The base SDK basically sets the OS version (this will be the same regardless of whether you are running the app on simulator or device). You should be chaining the build settings to device only if the device is connected and if you have installed the appropriate provisioning profiles.