-
Notifications
You must be signed in to change notification settings - Fork 894
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
iOS18.2 #196
Comments
I also need device support files for IOS 18.2. While I'm here, I'm running xCode on a Monterey so I'm limited to an older version. However, it should not matter if I manually add the 18.2 device support files to get my app working on my iPhone, right? |
@SUWW and @Hercuz Have you tried this: https://github.com/filsv/iOSDeviceSupport/blob/master/README.md#ios17workaround ? This is the only tip that could work, otherwise - you'll need to update Xcode :( |
@filsv Tried pretty much everything, unfortunately I updated my phone from 17 to 18.2 before I knew it would become problematic with Xcode. What I've read and understood, if you have the latest version of iOS on your iPhone you have to update Xcode to the latest version as well. However like I mentioned, if somebody could upload the device support files for iOS 18.2 it would enable me to create the app. My girlfriend has an iOS version from 17, which I tried to upload my app to with the workaround. However my Xcode 14.2 only has support for 16.2. I downloaded the device support files and it still wouldn't work. I did try to name a file 18.2 and copy the 16.2 files for my iPhone and it would give me another error than "Can't find support files...". Perhaps I'm being naive now, but can't just somebody who has access to the latest version of Xcode copy and paste the files? Or must it be "decrypted" or something like that? Alternative solutions are appreciated(not going back to an older version of iOS on my phone)! |
Hello, xcode14.3.1 is running on iOS 18.2 on a real machine. Is there any relevant Xcode iPhone OS Device Support available?
The text was updated successfully, but these errors were encountered: