-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 14 build error: Stored properties cannot be marked potentially unavailable with '@available' #1216
Comments
NOTE: This comment is auto-generated. Are you sure you have already searched for the same problem? Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem! If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue. In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding Following these steps can save you, me, and other people a lot of time, thanks! |
After doing some experimentation, I believe the most straightforward approach would be to wrap the class around another class that will instantiate two different versions of the UserScript class, one specifically meant for iOS 14+ and the other for versions less than iOS 14. |
@pichillilorenzo is there any work around until the issue get fixed? |
This is not really a workaround but might be helpful to someone, for now, you can just build through Xcode 13 after installing the Xcode 14 beta which comes with iOS 16 device support that is actually compatible with Xcode 13. In other words, you can build (for testing) for iOS 16 targets from Xcode 13 after you install the 14 beta alongside it. However, flutter run does not work so you always need to build through Xcode (you lose hot reloading) which might be a hassle. |
Code Eagle's open PR resolves this issue. |
also exists on the Xcode 14.0 stable version Temporary solution: |
I've simply fixed it by updating the platform to iOS 14 in Podfile. |
@mirkancal but this means that you only support iOS 14 and higher I used another git repo wich already has the fix included as workaround
|
@riegersan yes. 7 years old iPhone 6s has iOS 14. I'm okay with it. |
I fix update target 14 in file ios/Podfile |
How to fix it to avoid pods Signing & Capabilities again?
|
@blue492 it seems like the package is asking higher iOS target. What's your target? It's in podfile, beginning of the file, in the line: I'm also manually increasing with the Podfile script.
|
Released version |
this repo not exits. |
this was helpfull. Thanks:) |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue. |
Environment
Device information:
Description
When attempting to compile with the new Xcode beta, the following error prevents us from completin.g the build
Expected behavior:
No error
Current behavior:
Throws build error: Stored properties cannot be marked potentially unavailable with '@available'
Steps to reproduce
Images
The text was updated successfully, but these errors were encountered: