Invalid Swift Support xcode 8 itunesconnect issue - swift

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.

Related

App Store Connect: ITMS-90492: Invalid WatchKit Support

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.

Xcode 7.2 Invalid Swift Support - The SwiftSupport folder is missing

This might be some old issue already, but i've been working up for quite few days to fix this now. After submitting app to appstore i get this email :
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.
I've tried some suggestions as given in the similar questions at
- first - second - third and more
most of them suggested trying "Embedded content contains Swift" or update "command line tools" or try manual "framework" fix but none worked.
Anyone found the solution yet?
If you have used any Swift code in Objective C Project
then, go to Build Settings -> Embedded Content Contains Swift Code to Yes or vice-versa.
Then again archive your project and upload the new build to Appstore.

Submitting apps to app store for iOS9

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.

Lexical or Preprocessor Issue with Accounts framework

I recently installed the latest Facebook iOS SDK and included the Accounts framework for use with it. While I don't think the issue is related to the Facebook iOS SDK, I thought I'd mention it.
The error I'm getting when I compile now is this:
Pasting formed '_MAC#', an invalid preprocessing token
There are 3 of these errors, all within the Accounts framework header files that I cannot edit.
I'm using the default compiler: Apple LLVM compiler 4.2 with XCode version 4.6.3
I tried researching this issue for hours to no avail.
UPDATE: I tried compiling with Apple LLVM compiler 5.0 in XCode 5 Beta and I get even more compiler errors related to the Accounts framework.
UPDATE: I started a totally new project and rebuilt it from scratch. The same issue persists. As of now, it seems like my only option is to not use the new Facebook SDK or Accounts framework. I'm surprised no one else has this issue.
Have you set the Accounts.framework as "optional" under target settings?
Make it "Optional" and then Clean, Build and Run Project.
Solved it. I had a #define that looked like this in the pch file:
#define NA #"-"
Note to self. Do not use short define names in global header files.

Will old source code run with SDK 4.2?

I've been working on creating my own iPhone app with source code my company gave me. This code was created with iPhone SDK 3.0. I've worked on it for over a year (I'm a designer so my coding is mostly copy and paste) and to test the app on my iPhone it says I must update my SDK to 4.2. I'm wondering will this break my app? I probably don't have the skills in xcode to upgrade my code if I am required to rewrite parts.
Thanks,
Chris
If none of the code has been deprecated, changed or even removed, chances are good it still runs fine. Most projects run, and if you have used external code (and hopefully noted where you got it from) there might be an update available for that piece of code.
Just set the deployment target to iOS 3.0 in your project settings
here some little explanation: link