How to silence a warning in swift

Question

I have a piece of code which is generating lots of warnings (deprecated API)

Using clang* I could do

#pragma clang diagnostic push
#pragma clang dia         


        

Answer 1

Actually, you can suppress these warnings by using @available in the enclosing logical structure (i.e. function/type).

For example, say you have some code which uses the AddressBook framework, but you're building against iOS 9.

@available(iOS, deprecated: 9.0)
func addressBookStatus() -> ABAuthorizationStatus {
    return ABAddressBookGetAuthorizationStatus()
}

As of Xcode 7.0.1 this will prevent the inline warnings from being displayed.

Answer 2

As of 2020, Xcode 12.0, the consensus is that there is no way to achieve that.

I'll update/edit this answer if Apple add the feature.

Put it in your wish list for WWDC 2021 !

Answer 3

While there’s no way to silence deprecation warnings in Swift for now, technically you can do that for a particular symbol by editing the header file.

• Copy the deprecated symbol name
• Select File > Open Quickly

• Paste the symbol and press Enter

  Make sure the Swift icon is disabled in the Open Quickly box

• Select File > Show in Finder

• Change file permissions to allow editing if necessary
• Edit the deprecation macros for the symbol. See surrounding APIs for reference. E.g. replace:

__OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_6, __MAC_10_10, __IPHONE_3_0, __IPHONE_8_0)

with

__OSX_AVAILABLE_STARTING(__MAC_10_6, __IPHONE_3_0)

Now there’s one less distracting warning you can do nothing about.

I know, it’s dirty. But if there’s no replacement API available in the current SDK, it should be safe. Once a new version of Xcode comes out, the change will get overwritten and you will see the warning again. Then you can test the new SDK and OS to make sure the deprecated API is still available and did not get a replacement.

Please comment if you can come up with any downsides.

Answer 4

There is no general construct to silence deprecation warnings in Swift, but there is a workaround that can be applied in many cases.

Let's say you have a method getLatestImage() on class Foo which uses deprecated methods/classes.

Use @available as Daniel Thorpe described to silence all the warnings inside the method:

@available(iOS, deprecated: 9.0)
func getLatestImage() -> UIImage? {
    ...
}

Now you would like to call the method getLatestImage() without having a deprecation warning. You can achieve that by first defining a protocol and an extension:

private protocol GetLatestImage {
    func getLatestImage() -> UIImage?
}
extension Foo: GetLatestImage {}

And then call the method without a deprecation warning (if foo is an instance of Foo):

(foo as GetLatestImage).getLatestImage() // no deprecation warning

The result is you have Swift code that uses deprecated API without any deprecation warnings.