In Swift 4, tuples are treated more stricter than ever. This closure type: (Void)->Void means a closure which takes a single argument, of which the type is Void returns Void, meaning returns no value So, try any of the followings: Pass a value of type Void to the closure. (An empty tuple () is the … Read more
Reason The problem appears because from ios 11 UIBarButtonItem uses autolayout instead of dealing with frames. Solution You should add width constraint for this image-button if you use Xcode 9. button.widthAnchor.constraint(equalToConstant: 32.0).isActive = true button.heightAnchor.constraint(equalToConstant: 32.0).isActive = true PS button is not UIBarButtonItem, it is UIButton inside UIBarButtonItem. You should set constraint not for UIBarButtonItem, … Read more
I was able to get around the problem by simply calling invalidateIntrinsicContentSize on the UITabBar in viewDidLayoutSubviews. -(void)viewDidLayoutSubviews { [super viewDidLayoutSubviews]; [self.tabBar invalidateIntrinsicContentSize]; } Note: The bottom of the tab bar will need to be contained to the bottom of the main view, rather than the safe area, and the tab bar should have no … Read more
I think this ‘bug’ may be a Swift 4 ‘feature’, specifically something they call ‘Exclusive access to Memory’. Check out this WWDC video. Around the 50 minute mark, the long-haired speaker explains it. https://developer.apple.com/videos/play/wwdc2017/402/?time=233 You could try turning the thread sanitizer off in your scheme settings if you’re happy to ignore it. However, the debugger … Read more
UIColor(named: “myColor”) Source: WWDC 2017 Session 237 —— What’s New in MapKit Caveat: Your project’s Deployment Target needs to be set to iOS 11.0.
It’s hard to find the UI code which is not executed in main thread sometimes. You can use the trick below to locate it and fix it. Choose Edit Scheme -> Diagnostics, tick Main Thread Checker. Xcode 11.4.1 Click the small arrow next to the Main Thread Checker to create a Main Thread Checker breakpoint. … Read more
I was getting the same warnings even without multiple languages in my app, which led me to find out what was really going on. . . There are a few different things going on here. I was able to silence the fixed-width warnings in my own app by changing the width of the object spacings … Read more
I figured it out but Apple didn’t make it so obvious. The callback function from the delegate AVCaptureMetadataOutputObjectsDelegate has been renamed and the parameter names are different! So, replace func captureOutput(_ captureOutput: AVCaptureOutput!, didOutputMetadataObjects metadataObjects: [Any]!, from connection: AVCaptureConnection!) to func metadataOutput(_ output: AVCaptureMetadataOutput, didOutput metadataObjects: [AVMetadataObject], from connection: AVCaptureConnection) My view controller is now … Read more
I got rid of this warning by changing the “Swift 3 @objc Inference” build setting of my targets to “Default”. From this article: Before Swift 4, the compiler made some Swift declarations automatically available to Objective-C. For example, if one subclassed from NSObject, the compiler created Objective-C entry points for all methods in such classes. … Read more