I ran brew install xcode-kotlin first and then when I run xcode-kotlin install I get following (crash report hopefully uploaded short while ago) . This is M1 device fwiw. Currently have Xcode 13.4 installed.

Installing 1.2.0.
xcode-kotlin has crashed, do you want to upload the crash report to Touchlab? y/n: y
Uploading crash report.
Upload successful

Hey folks, My team has been using this plugin reliably for a year or so but recently we've found when we set breakpoints in our shared Kotlin code and press run the breakpoints turn to the dotted blue outline state indicating that the code is never executed/compiled - it definitely is getting executed!

We've tried uninstalling and reinstalling the plugin through the CLI as well as reinstalling with Homebrew but with no luck. We've also reimported the folder references to the shared code in our Xcode project too.

Interestingly the KaMPKit sample project breakpoints perfectly fine. Any ideas on how to resolve?

Details

xcode-kotlin info

Installed plugin version:	1.2.1
Bundled plugin version:		1.2.1

Language spec installed: Yes
LLDB init installed: Yes
LLDB Xcode init sources main LLDB init: No

Installed Xcode versions:
✔	Xcode 14.2 (14C11a)	C91F3560-00E7-4749-8E3F-4D83B1496051	/Applications/Xcode.app

In addition we've also made sure our preprocessor macros for debug is set to: DEBUG=1.

Expected result

Breakpoints get triggered when code is executed.

Current state

Xcode is indicating that the code is never executed.

Screenshots

We should add a CLI that would get installed using Homebrew. There's two ways we could make it work and we should decide which one is better.

Bundled mode

In the bundled mode, the plugin files are included with the CLI binary when downloaded by Homebrew. Installing the xcode-plugin formula would automatically put the plugin to the right place. The CLI would then have a single purpose, to update the DVTPlugInCompatibilityUUIDs entry in the plugin's Info.plist file.

1. Running xcode-plugin repair [xcode path,...] a. Loads UUIDs of all currently installed Xcodes and those provided manually. b. Updates the DVTPlugInCompatibilityUUIDs entry in the installed plugin.
2. Running xcode-plugin repair --only [xcode path,...] a. Loads UUIDs of only the Xcode paths provided manually. b. Updates the DVTPlugInCompatibilityUUIDs entry in the installed plugin.

When new changes to the plugin, users would run brew upgrade xcode-kotlin which would perform the same steps as the initial install, updating both the installed plugin and the CLI.

Independent mode

In the independent mode, the plugin files live in a separate repository from the CLI. It's up to additional discussion whether the plugin would be installed during the CLI's installation by Homebrew.

The plugin would then have the following features:

1. Running xcode-plugin install [version] (xcode-plugin update would do the same) a. Downloads the latest plugin (or the version specified) from GitHub repository. b. Loads UUIDs of currently installed Xcodes and updates the DVTPlugInCompatibilityUUIDs plist entry. c. Copies the modified plugin to the plugins folder
2. Running xcode-plugin repair [xcode path,...] a. Loads UUIDs of currently installed Xcodes and those provided manually. b. Updates the DVTPlugInCompatibilityUUIDs entry in the installed plugin. c. Fails if the plugin is not installed yet.
3. Running xcode-plugin repair [xcode path,...] a. Loads UUIDs of only the Xcode paths provided manually. b. Updates the DVTPlugInCompatibilityUUIDs entry in the installed plugin. c. Fails if the plugin is not installed yet.

So far the plugin has worked great for me, but I think there is an opportunity to make it even smoother. I have a Kotlin/Native project that generates an xcframework which I then pull in via swift package manager. When I have the Kotlin/Native project locally and registered as a Folder Reference in XCode it works great, but on a new machine where I don't have the original repo synced I cannot easily add breakpoints. Because SPM is based on the git repo it already is syncing all of the .kt files associated with the xcframework. Is there an easy way to make the plugin have access to these files? It would make it much easier for an iOS developer to debug the internals without needing a lot of additional steps.

The files get synced to /Users/username/Library/Developer/Xcode/DerivedData/Packagename-byqdevosfmstyigxngorlffhsqub/SourcePackages/checkouts

Xcode 11 required installing scripts where Xcode was installed. Before and after 11, the files can be installed at ~/Library/Developer/Xcode. I don't know if there is more than one of those folders if there are multiple versions of Xcode installed. If somebody has multiple versions of Xcode (I usually do, but apparently not today), see if there are multiple directories under ~/Library/Developer/.

I've recently upgraded from Xcode 12.3 to 13.1 and the debugging and syntax formatting is no longer working for me. I've tried re-running the setup script and re-importing my kotlin folders with no success. Has anyone else experienced this?

It would seems as though the latest update to xcode, 12.3, has broken support for xcode-kotlin. I've tried removing and reinstalling the plugin. When booting xcode, I no longer get the prompt to load the plugin bundle.

While the DVTPlugInCompatibilityUUID seems to be included in the Plugin Plist, (A74FBA51-FFEA-4409-B976-6FC3225A6F64), Xcode does not seem to approve of that Plugin. Upon Clicking "Load Plugin", Xcode quits, and upon new launches, it will display the dialog to load the plugin, but then immediately quit without the plugin.

I am using master@aa6bfba

Not sure exactly why, but sometimes the pointer isn't valid. I'm not sure if this is for any data, just arrays, or whatever. The old "check" method would simply skip over invalid pointers. That may be fine, but I'd like to understand what's actually happening.

I'd like the team to try this out. Hopefully we can find any significant bugs before release.

I think we can merge to main before testing, but I don't want to be out in main too long before we announce.

Most users we'll get to the page will be used to the current install. Add a "what's new?" section.

• Homebrew install and update
• Local repair on Xcode updates
• Better diagnostic info if there are issues

Hi!

I've installed plugin from CLI, added iosMain and commonMain as it's suggested in video tutorial

I observe crashes in my release build in iOS, and for some reason I see kotlin files in stack trace, and I can set breakpoints

Debug build doesn't allow to set breakpoints at all.

Output of xcode-kotlin info:

`Installed plugin version: 1.2.1 Bundled plugin version: 1.2.1

Language spec installed: Yes LLDB init installed: Yes LLDB Xcode init sources main LLDB init: No

Installed Xcode versions: ✔ Xcode 13.2.1 (13C90b) 7A3A18B7-4C08-46F0-A96A-AB686D315DF0 /Applications/Xcode.app

✔ - plugin is compatible, x - plugin is not compatible Run 'xcode-kotlin sync' to add compatibility for all listed Xcode versions.`

I've seen how files in filetree look like on the video (with Koltin icon), it's not like that for me:

I've checked KaMPKitiOS project and it's working fine.

This project is big, its main contributor has left and I need to make some support fixes for it. Also I'm not very experienced mobile developer but I have been writing some backend/web development for several years.

Thank you for any help!

Explore being able to step into Kotlin from calling code (Swift/Objc). I'm pretty sure this isn't possible, but it's something we should explore.

See Slack for some context: https://kotlinlang.slack.com/archives/C3PQML5NU/p1654805821671169

Does anyone know if it is possible to extend Xcode's code completion capabilities beyond Swift/Objective-C? I have not done much research on this, but the fact that lldb integrations are possible at least makes the question seem worth asking.

In any case, if someone here is able to indicate that this is not a complete fool's errand, I'd be happy to run a spike on it and see where it goes!

• [ ] has-reproduction
• [x] feature
• [ ] blocking
• [ ] good first issue

Should make some installation and usage videos.

• [ ] Video installing the cli, then installing the plugin. Show the Load Bundle and explain
• [ ] Video adding source, and debugging. Explain that source built on different machines won't work in the debugger
• [ ] Video upgrading Xcode

Xcode 13.3.1 (13E500a) crashes on startup M1 Max MBP running macOS 12.3.1.

Attempted simply rerunning ./setup.sh to reinstall, but it did not solve the issue.

Solution was to remove the plugin from ~/Library/Developer/Xcode/Plug-ins and the spec from ~/Library/Developer/Xcode/Specifications. Xcode then opened successfully. Ran xcode-kotlin's setup.sh to reinstall. Xcode opens successfully.