Need help with xcode-kotlin?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

463 Stars 24 Forks Apache License 2.0 87 Commits 12 Opened issues


Kotlin Native Xcode Plugin

Services available


Need anything else?

Contributors list

Kotlin Native Xcode Support

Plugin to facilitate debugging iOS applications using Kotlin Native in Xcode. Defines Kotlin files as source code, with basic highlighting. Allows you to set breakpoints and includes llvm support to view data in the debug window. Xcode does not officially support custom language definitions, but they also don't explicitly block them.

We're Hiring!

Touchlab is looking for a Mobile Developer, with Android/Kotlin experience, who is eager to dive into Kotlin Multiplatform Mobile (KMM) development. Come join the remote-first team putting KMM in production. More info here.


There are 2 parts to Kotlin support: 1) debugging support and 2) language color and style formatting.

You need to tell Xcode that

files are source files, and run an lldb formatter script when debugging starts. Advanced users may want to do this manually, but if you have Xcode installed in the default place, you can run the setup script.

Xcode 11

For debugging support in Xcode 11, run the installation script:


Xcode 11 introduced several breaking changes from earlier versions, and some resolutions are still outstanding. If you're using Xcode 11, you need to move some files into a protected area. Some users may not want to do this, and may possibly not have permissions to do this. You'll need to run the formatting support script with sufficient permissions, which generally means

sudo ./

You can still debug Kotlin without formatting support, just FYI. This step is not required.

All Other Xcode Versions

For all other versions of Xcode, the following script will install both debugging and formatting support:


Kotlin 1.3.6x Issue

Using static frameworks and/or Cocoapods may remove debug info in this version. More info here

Special Note

All of that magic was sorted out by Ellen Shapiro, who understands all of this far better than I ever will.

Tracking Issue Here


If properly set up, you should be able to add Kotlin source to Xcode, set up breakpoints, and step through code.

We're deprecating the Xcode Sync plugin. Add folder reference instead! See issue. Description and video coming soon.

~~To help automate adding Kotlin source, check out the Kotlin Xcode Sync Gradle plugin.~~


The Droidcon NYC app has both the Xcode Gradle sync and Xcode projects enabled for debugging.


Setting up the Plugin has been an amalgam of various source projects, as Xcode "Plugins" are undocumented. The most significant piece, the language color file came from other color files shipped with Xcode. Xcode plugin file from GraphQL

LLDB formatting originally comes from the Kotlin/Native project, source, although the way data is grabbed has been heavily modified to better support an interactive debugger.

Possible Future Stuff

Color File

The color definition is basically Java's with minor additions. This could be better adapted to Kotlin.


It's a bash script, which works, but does not take into account non-standard install directories and various other possible config options. This could be improved.

From Swift

You can see variables when you're debugging Kotlin, but when you're in a swift file that has a class that came from Kotlin you can't see much. It would be great to be able to improve that.

Better Debug Alignment

This happens in the Kotlin compiler, so it's a little deeper, but the breakpoints don't always track with the source when there are more complex structures (lambdas, etc). This should improve over time.

Xcode Updates

Every time Xcode is updated we need the UUID. It needs to be added to

. To find the UUID of your version of Xcode, run the following:
defaults read /Applications/ DVTPlugInCompatibilityUUID

Info from here

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.