Xcode doesn’t support iOS 15.0 - ios15

I updated my iPhone to iOS 15.0 yesterday and I wanted to build in Xcode (version 12.5.1).
But in Xcode it is showing 'iPhone (unsupported OS version)' and when I try to build (command + R) then I get the error:
Xcode doesn’t support iPhone’s iOS 15.0 (19A346).
Is there a way to use it without downgrading iOS?

Without updating Xcode, you need to put the relevant device file in the DeviceSupport section and run Xcode again. DeviceSupport files are located here.
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
https://github.com/filsv/iPhoneOSDeviceSupport
You can download iOS15 devicesupport file from here, then you need to unzip, then you need to put it in DeviceSupport section on your mac.
When you restart Xcode, there should be no problem.
Update for iOS 15.1
For 15.1 devices, You can copy file from 15.0 to the same directory as 15.1. Then you need to open Xcode again, it should be fine.

The accepted answer's repository doesn't include some of the latest versions like 16.1, here is a more updated one:
https://github.com/iGhibli/iOS-DeviceSupport/tree/master/DeviceSupport

Related

Error being thrown when trying to debug from JetBrains Rider: error HE0004: Could not load the framework 'DVTITunesSoftwareServiceFoundation'

I am unable to debug a Xamarin.iOS application out of JetBrains Rider 2022.2.2. This is the error that gets thrown when trying to deploy to the simulator:
error HE0004: Could not load the framework 'DVTITunesSoftwareServiceFoundation' (path: /Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/DVTITunesSoftwareServiceFoundation):
dlopen(/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/DVTITunesSoftwareServiceFoundation, 0x0001): Library not loaded: '#rpath/ContentDelivery.framework/Versions/A/ContentDelivery'
Referenced from: '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/DVTITunesSoftwareServiceFoundation'
Reason: tried: '/usr/lib/swift/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Library/Frameworks/Xamarin.iOS.framework/Versions/15.12.0.2/lib/mlaunch/mlaunch.app/Contents/MacOS/../Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/usr/lib/swift/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Library/Frameworks/Xamarin.iOS.framework/Versions/15.12.0.2/lib/mlaunch/mlaunch.app/Contents/MacOS/../Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/System/Library/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file)
I had the same problem.
Let me guess... You just upgraded to XCode14 and the corresponding Command Line Tools?
Downgrading XCode and Command Line Tools to 13.4.1 helped me.
What worked for me
Go To https://developer.apple.com/download/all/?q=command%20line%20tools
Download XCode and Command Line Tools for Xcode 13.4. Unpack Xcode (13.4.1) and rename it (for example Xcode 13) and place it parallel to Xcode (14) in the programfolder.
.
Then install the Command Line Tool.
Now in Xcode (still 14) > Preferences > Location > Command Line Tools, select version 13.4.1 instead of 14. You can see the Path for it is "Application/Xcode 13".
For safety restart tools, and it worked again...
Update: With the last update of Visual Studio, the downgrade was no longer necessary for me. Since then I can build the apps with XCode 14 and the corresponding command line tools without any problems. So I suggest upgrading Visual Studio to the latest version first.
Here is how I made it work:
Download the former version here (note: you need a developer account)
Double-click on the downloaded .xip file to install XCode 13.4.1
Rename the newly installed XCode application into Xcode.13.4.1.app and move it into your Applications folder
Open the usual XCode application and go to the preferences
In the locations tab you will be able to select XCode 13.4.1 for Command Line Tools
Redownload Visual Studio?
It turns out Microsoft released a brand new Visual Studio at some point.
We haven't been in our Xamarin project for a while and even though it said there were no updates, no Simulators were showing up.
Our Visual Studio said the version was 8.10.25 yet when I was reading the release notes, they referred to version 17.3.7.
Our team had to download Visual Studio again and then we saw the version updated to 17.3.7.
So check your version of Visual Studio and redownload the newest one. That's what fixed this issue for us.
Latest update fixed the issue for me.
I had the same issue, while searching for answer I found this thread,
writing this to confirm that I took the latest update on 9th nov(NET 7 SDK). Issue seems resolved with latest update.
There is a more elegant solution to this problem. You need to upgrade Xamarin.iOS manually. The releases are on GitHub 16.0.0.72 did the trick for me.

Android Studio 4.1 Canary 9 201.6466190-linux distribution corrupted?

At first I've tried to update Android Studio 4.1 Canary 8 to Canary 9 as usual through update dialog. At the first start Canary 9 have thrown error:
Missing essential plugin:
org.jetbrains.android
Please reinstall Android Studio from scratch.
So I downloaded Canary 9 distribution from official source (https://developer.android.com/studio/preview). Deleted Canary 8 catalog and extracted tar.gz with Canary 9. Then launched android-studio/bin/studio.sh with the same error.
I renamed ~/.AndroidStudioPreview4.1 catalog and started studio once more. Same error.
Now I rolled back to Canary 8 from my backup.
Any help how to move from Canary 8 to 9?
Basically this issue mentioned in release notes
In Android Studio 4.1 Canary 9, you may see the following error when
first launching Android Studio after upgrading:
missing essential plugin org.jetbrains.android
This can happen when you import your settings from a previous version
of Android Studio. Typically, this means you have a locally installed
Kotlin plugin that is not compatible with the new IDE.
To fix this issue, remove the Kotlin directory from the following
locations:
Linux: ~/.local/share/Google/AndroidStudioPreview4.1
Windows:
C:\Users\YourUserName\AppData\Roaming\Google\AndroidStudioPreview4.1
MacOS: ~/Library/Application Support/Google/AndroidStudioPreview4.1
Because there is no Kotlin plugin compatible with Canary 9 currently
available from JetBrains, we have bundled our own Kotlin plugin with
the Canary 9 update, so you don't need to manually install a Kotlin
plugin.
source
At the same time by path ~/.local/share/Google/AndroidStudioPreview4.1 no such file or directory. The only catalog named AndroidStudioPreview4.1 founded by ./.cache/Google/AndroidStudioPreview4.1. So I deleted it without any effect on subject issue.
Then I completely removed ~/.AndroidStudioPreview4.1 instead of renaming which I'd done before. And resolved the issue.
I believe Google bundle Kotlin plugin in a different way JetBrains do. So paths differ. Maybe path for Windows to. I believe paths should be corrected in release notes.
Solution:
rm -r ~/.AndroidStudioPreview4.1
Solved this problem by using terminal in Ubuntu 18.04.5 LTS
toumbou#toumbou-Aspire-V3-471:~$ cd ~/.AndroidStudio4.0/config
toumbou#toumbou-Aspire-V3-471:~/.AndroidStudio4.0/config$ ls
codestyles disabled_plugins.txt inspection plugins tasks user.token
colors disabled_update.txt options port.lock terminal workspace
toumbou#toumbou-Aspire-V3-471:~/.AndroidStudio4.0/config$
and open the file via nautilus
toumbou#toumbou-Aspire-V3-471:~/.AndroidStudio4.0$ nautilus config
Then move the config folder and remove also the kotlinRefractoring.xml and also I removed the caches of my previous project so now I got it running fine again with some tweaks all things ares fine.

Not able to connect adb after upgrate Android Studio to 3.4

unable to connect to adb.check the event log for a possible issue, verify that localhost entry is pointing to 127.0.0.1 or:: 1 for ipv4 or ipv6
Tried adb kill-server, restart, invalidate restart nothing works.
Same issue reported over here https://issuetracker.google.com/issues/130791561
Note: I have not added any file or anything in studio, it's fresh installed Studio after format a full system still issue is there.
Replace your platform-tools with this one and delete the other one.
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
I was also facing this issue in android Studio 3.4 version, but now I have fixed it , if you are using windows then follow these steps:
Download Platform tools from here
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
Extract downloaded zip file
Go To location "C:\Users\your_computer_user_name\AppData\Local\Android\Sdk" and Delete "Platform tools" folder
Copy and Paste, downloaded platform tool folder to above location
Now Go to your android studio and Rebuild your project Then run.
For Mac Users, follow these simple steps :
Just simply Navigate to Tools > SDK Manager> Android SDK>, then click on the Tab of SDK Tools, then look for Android SDK Platform-tools and update it.
Then the last step, Invalidate cache and restart your IDE, after that, then finally you restart your Mac. (Sometimes it's this step is unnecessary)
It will work out successfully.
Solution for Linux Users.
System info: Linux Mint Cinnamon 19.1 , Android Studio 3.4.1
Issue description: Problem with platform tools.
Solution: Remove the folder manually and update SDK tools through Android Studio.
Step 1: Go to your Android SDK installation folder. By default under your home directory. Choose platform-tools and simply delete. (/home//Android/SDK)
Step 2: Open Android Studio and go to SDK Tools. (File -> Settings -> Appearance & Behaviour -> System Settings -> Android SDK -> SDK Tools) By the moment you should be able to see Android SDK Platform Tools line unchecked.
Step 3: Put a check to install Platform Tools and press OK. Notice it'll relocate the folder to the directory where deleted.
Now that you re-installed the platform tools, restart the Android Studio and your deployment targets should show up.
If you don't install the platform tool back and ever try to build or run a project you'll get this IDE error. Just FYI :)
So that's all. Enjoy.
Happy coding
If you use Windows, you might have a corruption in api-ms-win-crt-runtime-l1-1-0.dll.
Try to update it - you can get the update from Microsoft's website.
You should check it - path/to/sdk/platform-tools and try to run adb.exe
When you update Sdk platform tools(which contains adb.exe) to release 28.0.2 and if you are using windows 8.1 then it needs few updates from windows.
As per SDK Platform tools release notes(https://developer.android.com/studio/releases/platform-tools):
Updated Windows requirements : The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package."
Windows update url: https://support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
Prerequisite for Windows update url: https://www.microsoft.com/en-us/download/details.aspx?id=42327
Faced the exact same issue but after updating with prerequisite url first then the other url provided now it is working perfectly fine for me.
It worked for me by selecting -> Use libusb backend
This worked for me on Windows:
Goto cmd write %temp% hit enter -> delete all data from there.
Restart your Computer.
Open Android Studio now, it will work.
Clear all cache memory (related to Android Studio)
Restart ADB manually from Android Studio (first option)
Open Command prompt and got android sdk>platform-tools> adb kill-server
press enter
and again adb start-server
press enter
Restart ADB manually form Android Stidio (second option)
go to your (SDK store path) sdk>platform-tools>adb
press enter
ex. D drive > sdk>platform-tools>adb
Restart your system
Delete the platform-tools folder from the sdk and replacing with the same from your another pc. I am also facing this problem after updating to 3.4. If you face same problem please update to Android Studio 3.5 Canary Channel.
The reason is for ADB server problem. Simply re-run your adb.
(Go to your SDK folder then inside platform-tools folder you can see adb.exe. copy the path location and paste it in your computers system Environment variable. Set a new path there and paste the adb.exe file location there. hope it will solve )
If you are using Genymotion, there is an update that fix the problem.
Genymotion 3.0.2 (April 18th, 2019)
Corrections
We have fixed an
incompatibility with the adb tool bundled in the platform-tools 28.0.2
package of the Android SDK, which caused failures to start virtual
devices.
This new version of adb changed the behavior of the “adb connect
:” command by making the “port” part mandatory. This
broke Genymotion Desktop in a few places where it did not pass the
port. We have adjusted the way we call “adb connect” and also updated
the version we ship with the product to match the one in
platform-tools 28.0.2.
If non of the above answers worked for you (as same happend to me), down grade to the old version of Android Studio by following these steps:
Uninstall current Android Studio
Go to Android Studio Archive and download any older version
After installation, Open the project. You might see an error like this
This version of Android Studio cannot open this project, please retry with Android Studio 3.4 or newer.
Now, open project gradle and update classpath tools.build version. I.e. in my case Android studio version is 3.2 and classpath 3.2.1
Hope it might save someone time.
I faced this issue last night, and I tried these methods to fix:
download older platform-tools and place it in the android sdk folder.(not work for me)
adb kill-server, adb start-server.(not work for me, adb had no response with these cmd)
kill the process that occupies port 5037.(for me, there is no other .exe run at this port)
reinstall platform-tools in Android Studio.(not work)
download ADB Kits and replace them in platform-tools folder.(work!!!)
It seems that my adb file has been modified or replaced by some programs. You can try these methods, and I hope some of them can work for you.
I had this issue only after a Genymotion update, on Mac.
What worked for me: Open Genymotion preferences, Select ADB, choose "Use custom Android SDK tools" and points to your Android SDK folder.
Actually the problem is not with the android studio version 3.4
Problem is with the android platform tools version which is latest one 29.
So install the previous version of the android platform tools version it will solve your problem. as above #Ved mentioned.
Ved link:
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
EndTask adb.exe from Background processes (TaskManager) and Run Application again.
It works for me

How to reset Android Studio to previous version

I recently recklessly updated AS from 3.0.1 to 3.1, but project manager says 3.0.1 is the version to be worked with in our project. Is there a way to reset AS to version 3.0.1 without having to uninstall it?
Currently there is no direct way with which a downgrade can be done. I managed to do the downgrade by downloading Android Studio 3.0.1 from here and then running the installer. It will prompt whether to uninstall previous version, and when you allow and proceed, it will remove 3.1 and install 3.0.1.
You need to ensure 3.1 is not running in background i.e. Close the Studio 3.1 application.
On Mac, just download desired version .app file from https://developer.android.com/studio/archive, then paste into Applications folder.
i also updated to Bumblebee .. just go to preferences and write "device manager" in search choose keymap and set a shortcut key for device manger click apply and ok and use the new shortcut to get the Avd menue

XCode 6 Beta will overwrite XCode 5.1.1?

I am about to install XCode 6 Beta and it asked to close the already running XCode 5.1.1.
Will it overwrite XCode 5.1.1,O or will XCode 6 be a separate installation?
No, it has a different name: Xcode6-Beta rather than the normal Xcode.
Yes it is a different installation.
It was the first time that XCode asked for installation after coping it to the Applications folder. Usually, after coping XCode from its .dmg file, I rename it and runs it.
I have several XCode versions in my Applications folder. I got confused when it asked to close the existing XCode 5.1.1 during installation, since it never happened before.

Resources