You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2022. It is now read-only.
I'm having some issue with debugging using SlackKit.
If I create a simple project using Swift package manager, setting SlackKit as a dependency, I can compile / run the project with no issues, but autocomplete is broken. For example within the private func handleMessage(message: Message) method, "message" autocompletes to <>.
I also notice that if I put a breakpoint in that same method, none of the local variables are shown in the debugger, and if I try to po some of them it gives a bunch of warnings like this:
warning: Swift error in module robot-or-not-bot.
Debug info from this module will be unavailable in the debugger.
The text was updated successfully, but these errors were encountered:
I think this is a SPM bug which has recently been fixed. If you're willing to use a development keychain it looks to be fixed in swift-3.1-DEVELOPMENT-SNAPSHOT-2017-01-31. A .xcodeproj file generated as follows should work:
Set your default keychain: $ export PATH=/Library/Developer/Toolchains/swift-3.1-DEVELOPMENT-SNAPSHOT-2017-01-31-a.xctoolchain/usr/bin:"${PATH}"
I'm having some issue with debugging using SlackKit.
If I create a simple project using Swift package manager, setting SlackKit as a dependency, I can compile / run the project with no issues, but autocomplete is broken. For example within the private func handleMessage(message: Message) method, "message" autocompletes to <>.
I also notice that if I put a breakpoint in that same method, none of the local variables are shown in the debugger, and if I try to po some of them it gives a bunch of warnings like this:
warning: Swift error in module robot-or-not-bot.
Debug info from this module will be unavailable in the debugger.
The text was updated successfully, but these errors were encountered: