Xcode 14 beta error: Stored properties cannot be marked potentially unavailable with '@available'

Question

I get this error when I run my app on Xcode 14 beta and I don't know how to fix it:

Stored properties cannot be marked potentially unavailable with '@available'

It doesn't pop up when I run Xcode 13, and the app runs smoothly. I am in the .xcworkspace file.

If the problem is in RevenueCat it isn't your code so there's nothing you can do. File a bug with the code authors and go back to Xcode 13. — matt, Jul 13 '22 at 18:41
Check this: https://stackoverflow.com/questions/64797366/stored-properties-cannot-be-marked-potentially-unavailable-with-available — LoVo, Jul 14 '22 at 06:58
I've fixed it like this: https://stackoverflow.com/questions/41904724/using-available-with-stored-properties/73699790#73699790 — mirkancal, Sep 13 '22 at 08:30

Vishnu · Answer 1 · 2022-09-14T10:50:21.247

21

I have this error in Flutter project in XCode 14. One of the external packages were using:

@available(iOS 14.0, *) My current fix is:

Update version in Podfile platform :ios, '14.0', pod update && Pod install

edited Sep 14 '22 at 10:50

answered Sep 14 '22 at 10:49

Vishnu

348
2
7

Is there a way to solving it not defining the iOS 14 as a global platform? – jed1 Sep 14 '22 at 19:25
In my code happened this issue was resolved like what i mentioned above. please mention your exact issue. This issue only happened when i was updating the latest Xcode version. @jed1 – Vishnu Sep 16 '22 at 07:12

score 13 · Answer 2 · answered Sep 30 '22 at 12:04

In Xcode 13, and lower, you were able to compile if you used a lazy @available stored property as such:

@available(iOS 10.0, *)
private(set) lazy var center = UNUserNotificationCenter.current()

However, this does not work in Xcode 14.

Instead, you need to use a non-available stored property, and use a computed @available property:

private var _selectionFeedbackGenerator: Any? = nil
@available(iOS 10.0, *)
fileprivate var selectionFeedbackGenerator: UISelectionFeedbackGenerator {
    if _selectionFeedbackGenerator == nil {
        _selectionFeedbackGenerator = UISelectionFeedbackGenerator()
    }
    return _selectionFeedbackGenerator as! UISelectionFeedbackGenerator
}

Answer source

score 12 · Answer 3 · answered Dec 12 '22 at 11:35

Let me tell you 100% working solution if this error is being raised due to DKImagePickerController.

Follow these steps:

Goto your Podfile and replace this https://github.com/miguelpruivo/DKImagePickerController.git url with this https://github.com/zhangao0086/DKImagePickerController.git url.
In your flutter project run following commands:
2.1) flutter clean
2.2) flutter pub get
Navigate to ios folder and run following commands:
3.1) pod install (use arch -x86_64 pod install if you are using M1)
3.2) pod update (use arch -x86_64 pod update if you are using M1)
Run your project.

True story! This is the best solution for this project. This has happened due to some project discontinuation as I can remember. Thanks for documenting. — Randika Vishman, Apr 27 '23 at 08:56

score 11 · Answer 4 · answered Oct 05 '22 at 20:09

11

In my case the problem was in flutter_inappwebview package. I've fixed it by using the newest version - 5.4.4+3

https://pub.dev/packages/flutter_inappwebview/install

answered Oct 05 '22 at 20:09

IvanPavliuk

1,460
1
21
16

3

this worked for me, I had `flutter_inappwebview` version 5.3.2, changed it to 5.4.4, `flutter pub get`, and it's working, thank you! – Halen Oct 11 '22 at 16:36
How did you use the newest version, what did you do? – gurkan stack Oct 15 '22 at 17:24
How can I install this package? – gurkan stack Oct 15 '22 at 17:24
There is no such a library in my pubspec.yaml. – gurkan stack Oct 15 '22 at 17:25

score 3 · Answer 5 · answered Sep 23 '22 at 12:18

3

Be sure to change both sections of the iOS Deployment Target in the Build Settings tab, like in my picture:

answered Sep 23 '22 at 12:18

George Lee

814
18
34

score 3 · Answer 6 · answered Sep 27 '22 at 00:02

3

I had the same problem. As directed by the repository on GitHub, a workaround is to update the Podfile version: platform :ios, '14.0'

answered Sep 27 '22 at 00:02

Renato Leal

181
2
4

score 0 · Answer 7 · answered Mar 21 '23 at 17:12

Brother, I just find a solution for my project, It may comes to you workaround, but I still would like to share my experience about it;

class MyClass {
    @available(iOS 15.0, *) // Stored properties cannot be marked potentially unavailable with '@available'
    var myProperty: String
}

Xcode offers us entire class to make @available

@available(iOS 15.0, *)
class MyClass {
    var myProperty: String
}

This is my workaround solution. You can use the @available attribute on its getter and setter methods instead of the property itself.

class MyClass {
    private var myValue: String = ""
    
    @available(iOS 15.0, *)
    var myProperty: String {
        get {
            return myValue
        }
        set {
            myValue = newValue
        }
    }
}

This is from my real project;

score 0 · Answer 8 · answered Jun 08 '23 at 07:57

0

My case:

Remove ios folder. (Should save your Info.plist)
flutter create .
Change ios to 14. (Pod file)
flutter pub get => cd ios => pod install => cd .. => flutter run

answered Jun 08 '23 at 07:57

Thang Tran

171
1
5

Xcode 14 beta error: Stored properties cannot be marked potentially unavailable with '@available'

8 Answers8

Linked