xcode8.1

Xcode 8 binary is not Showing on itunesconnect for Review

十年热恋 提交于 2020-01-11 09:17:10
问题 I have made Binary file from Xcode 8 and upload to App Store through Application Loader(3.6). Also it is submitted successfully with pop up. But the Binary is not showing in iTunesConnect since it crosses 19 hour yet it is not showing in itunesconnect. Please Help me out from this situation @update Here is my Plist file 回答1: I faced same issue. I was using client's account and submitted builds. I got Upload Successful popup but builds were not shown. This happens because there are privacy

Xcode 8 binary is not Showing on itunesconnect for Review

寵の児 提交于 2020-01-11 09:16:16
问题 I have made Binary file from Xcode 8 and upload to App Store through Application Loader(3.6). Also it is submitted successfully with pop up. But the Binary is not showing in iTunesConnect since it crosses 19 hour yet it is not showing in itunesconnect. Please Help me out from this situation @update Here is my Plist file 回答1: I faced same issue. I was using client's account and submitted builds. I got Upload Successful popup but builds were not shown. This happens because there are privacy

EXC_BAD_ACCESS error for invoking method in swift

青春壹個敷衍的年華 提交于 2019-12-25 04:25:01
问题 Here is the code: import Cocoa @NSApplicationMain class AppDelegate: NSObject, NSApplicationDelegate { @IBOutlet weak var window: NSWindow! @IBAction func changeBtn(_ sender: NSButton) { obj1.changeColor() obj2.changeBackgroundColor() objFld1.textColor = obj1.color objFld2.drawsBackground = true objFld2.backgroundColor = obj2.backgroundColor } @IBOutlet weak var objFld1: NSTextField! @IBOutlet weak var objFld2: NSTextField! class colored { var color = NSColor.black var backgroundColor =

ld: library not found for -lGoogleToolboxForMac

℡╲_俬逩灬. 提交于 2019-12-23 07:47:21
问题 I am implementing firebase setup via pods. My Pods file looks like following one. # Uncomment the next line to define a global platform for your project platform :ios, '8.0' # $(PROJECT_DIR)/build/Debug-iphoneos/GoogleToolboxForMac lib search path target 'ProductName' do # Uncomment the next line if you're using Swift or would like to use dynamic frameworks # use_frameworks! # Pods for mCura pod 'Firebase/Core' pod 'Firebase/Messaging' end Everything is fine with iPad simulator. its running

Falling back to loading access token from NSUserDefaults because of simulator bug

偶尔善良 提交于 2019-12-18 13:53:14
问题 Xcode log show the above error while running in Xcode 8.1, ios 10.1. Is there any problem or should I ignore and continue? 回答1: I have this problem, too. It seems to be caused by an the Facebook SDK's Login Access Token. It caches just fine on a real device, but not on the simulators. Try running the app from a physical device. 回答2: You can ignore this warning, it's hard coded in the FacebookSDK when using the iOS Simulator. The SDK does contain a bug though which prevents the simulator from

Linker command failed with exit code 1 - duplicate symbol __TMRbBp

强颜欢笑 提交于 2019-12-17 23:16:57
问题 Since I've updated to Xcode 8.1 I can't archive and also not run in Release mode (in debug mode its working). The error is that there are several "duplicate symbols for architecture arm64" and all are "duplicate symbol __TMRbBp". Whats that? 回答1: It seems to be a bug in Swift. See discussion on Apple developers portal It is said to be fixed in Xcode version that is about to be released. But for now there is temporary workaround: Go to your target Build Settings and set Reflection Metadata

In Swift, what's the difference between calling UINavigationController() vs UINavigationController.init()?

流过昼夜 提交于 2019-12-17 14:22:40
问题 In Swift, what's the difference between calling UINavigation() vs UINavigation.init() ? They both seem to return valid instance of UINavigationController . 回答1: UINavigationController() and UINavigationController.init() are the exact same thing. You can verify this by typing both into a Playground and then option -clicking on them. Both bring up the documentation for the same initializer. The Swift convention is to use just the type name (without .init ). 回答2: For some given type (e.g.

Linker Error After Updating swift Version and pods

久未见 提交于 2019-12-12 15:18:29
问题 I am installing Alamofire with pods and getting compile time error. There are a lot of questions regarding this but: Deleting the derived data & updating pods won't work for me. This is the error: Alamofire/Alamofire.framework/Alamofire compiled with newer version of Swift language (3.0) than previous files (2.0) for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) 回答1: Update following things in your pod files: source 'https://github.com

How to perform sequential request with Alamofire and update a progressHUD at every step in Swift 3

假如想象 提交于 2019-12-12 04:12:16
问题 Ok, I am going nuts over this one... I'm using Alamofire 4.x (Swift 3 and XCode 8.1). I need to fetch and parse several html requests from a site that requires authentication (no json API, unfortunately). The HTML is then parsed with Fuzi and this progress can take some time so I plan to use a ProgressHUD (PKHUD to be exact) to let users know about what is going on. I also need to grab some html that is not behind an authentication. I created a struct and functions to handle the overall

Swift stdlib tool Error

社会主义新天地 提交于 2019-12-06 16:51:10
问题 I'm getting this error on compilation with Xcode 8.1 and Swift 3: Swift stdlib tool Error The end of the compile log looks like: /Users/..../Library/Developer/Xcode/DerivedData/.../Build/Products/Debug/.../Contents/Frameworks/libswiftCore.dylib: replacing existing signature /Users/..../Library/Developer/Xcode/DerivedData/.../Build/Products/Debug/.../Contents/Frameworks/libswiftCore.dylib: CSSMERR_CSP_INVALID_CONTEXT_HANDLE In architecture: x86_64 Probing signature of /Users/..../Library