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
Can't see my iOS device in IntelliJ running on macOS Catalina? #3950
Comments
Go to Preferences then Languages & Frameworks. Click on Schemas and DTDs. Then click on Flutter. You need to update your Flutter SDK path.... |
@RECKK1 Preferences then Languages & Frameworks shows my correct flutter path. there is no flutter option in Schemas and DTDs. |
Sorry for the lack of updates here. We don't yet have access to Catalina and I don't know when it is coming, so we can't really do anything currently. |
I was having this issue. However, I had already been running it successfully on Catalina. Something got an update (pretty sure it was xcode) and I could no longer user iOS sims. My solution was found by flutter doctor:
I already had xcode installed and updated for quite a while, so I just ran |
Working for me, thanks) |
This solved it for me—turning on developer mode
|
Last night I got an update and I update my machine to macOS Catalina. Then I upgrade my Xcode to 11. My app already on App Store and Google Play since April. Today I try to update my app and while trying to test on my iPhone 6 and iPhone X, I can't see my iOS device in IntelliJ. I run my app on iOS simulator and it was okay. Then I open the Xcode and run my app from there using my connected iPhone 6 and iPhone X. Its install my app on device with white screen. Than I kill my app and tab an run again an my app opens and works on my iOS device.
When will we can get a same option before that I can see my connected iOS device on IntelliJ? Thanks.
My flutter doctor -v output:
The default interactive shell is now zsh.
To update your account to use zsh, please run
chsh -s /bin/zsh
.For more details, please visit https://support.apple.com/kb/HT208050.
The text was updated successfully, but these errors were encountered: