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
[tool] connected IOS devices not visible on old version of Xcode, "Flutter requires Xcode 13 or higher" #104155
Comments
Hi @lel101, Thanks for filing the issue. Can you please share the output of |
@maheshmnj Thank you for your response stable 3.0.1
-- flutter devices
stable 2.10.5
-- flutter devices
|
Thanks for the info @lel101,
I believe you would need to upgrade xcode to 13, However, you can try this solution #41006 (comment) and see if it helps fix the issue ? |
@maheshmnj
I'm using an old mac, that's why I cannot upgrade my xcode :(
I will check this one thanks! |
I got same error too.. i have tried this.. but still not work in flutter 3. please confirm @lel101 have u tried it? |
@AbiMulLyA What version of xcode you are using ? |
@lel101 i'm using xcode 12.4 and currently on flutter 3.0.1 |
@AbiMulLyA |
@lel101 sorry i'm using old mac too. I can't update to xcode 13 😆 |
@maheshmnj Do you have any work around for laptop that uses xcode below 13 ? |
@maheshmnj is there another solution for this? |
Thanks for the info @lel101, I am not sure of any other solution to why the ios devices are not visible, The xcode version seems to be the cause of the issue. Labeling this issue for further insights from the team. |
I was just thinking about this in #103844 (comment) We could change the Xcode version logic from being so aggressive--only check if it's installed, then try to build or get devices or whatever, and only check and report the version if that fails. The last Xcode bump, for example, was because we need bitcode-enabled apps (usually add-to-app) to be on the same or newer version of clang than the one the engine is on. But for most of our users that's not relevant (bitcode is off in the template). Sometimes it just won't build on an old toolchain, at which point we can report that the version is too old. |
App Store does not accept archives built with Xcode < 13 anymore. I have a Mac Mini late 2012 and it doesn't support macOS Monterey. I got Monterey installed using the OpenCore Legacy Patcher and then I was able to install Xcode 13 without issues. You can check supported models here. |
That's one of the reasons we're enforcing it so strictly on Ideally everyone should be on the latest and greatest version of Xcode with the newest SDKs. In practice though it can be really difficult to, say, upgrade your entire CI suite hardware, when it only takes one new machine (or deployment service) to actually archive and publish. We could allow looser |
@lel101 could u run your project on iPhone real device with current flutter n xcode version? |
On the latest versions, Running
|
@dam-ease why are you tagging me? |
I saw a similar issue recently on the new Flutter version and error message, so I tagged you because I saw you add a priority label and thought you might want to follow up on this issue by keeping up to date with the latest information. Apologies if my assumption is incorrect. |
this approach does not scale well to the number of open issues that are labelled |
Sorry for the trouble.
It work's fine in flutter version 2.10.5 stable, but when I upgrade my flutter environment to 3 this problem occur, even though the emulator is already open.
But when I will downgrade the flutter version to 2.10.5 it will work again.
Btw I'm only using Xcode 12.4 because I have an old mac and I can't upgrade to Xcode 13 or higher.
The text was updated successfully, but these errors were encountered: