When trying to send message (bot.webApi?.sendMessage()) with text that has question mark (?) I get failure with unknownError type. When I removed this question mark my message got through. I think there is something wrong with escaping this sign from request url and it's messing with url query.

I'm a bit confused how one would observe changes on the Client. A callback api would be appreciated. Essentially when messages are handled my client, state changes and etc. how would one go about observing these changes in a controller?

I've just started playing around with SKWebAPI, and it seems like channelsHistory() fails since the whole family if channels* API methods is now deprecated and doesn't work for new apps already.

I'd love to work on this and port the deprecated methods from channel* to conversations*, but I'm fairly new to Swift and will need your help reviewing my PRs. Should I work on that?

Hi :)

I have some issues with the slackFormatEscaping function When I use it I am unable to make mentions because it escape the characters but after when URLQueryItem convert params it encodes this to Percent-encoding

For the moment I have fork all the repositories to remove this function, Am I wrong or Am i missing something ?

I actually need support for Attachments in the app I'm working on. @muratayusuke's fork has this actually already done along with a bunch of other enhancements: https://github.com/muratayusuke/SlackKit/commit/0baf74dacb98c6a4d3186ef4ce2370bc5741e40d

Would love to see a PR @muratayusuke to pull his fork's changes into upstream. If not I can always make a PR just for the Attachment support but really it would just be duplicating @muratayusuke's efforts. Thoughts?

The code I'm running to run is simple:

let bot = SlackKit()
bot.addWebAPIAccessWithToken(token)
bot.webAPI?.conversationsList(success: { channels, nextCursor in
    print(channels)
}, failure: { error in
    print(error.localizedDescription)
})

I traced the URLRequest being sent and it seems like the url is: https://slack.com/api/conversations.list?token=xoxb-SLACK-BOT-TOKEN

I tried sending this same request with Postman and got this response:

{
    "ok": false,
    "error": "invalid_auth"
}

But when I send a request to https://slack.com/api/conversations.list with the following header:

Authorization: Bearer xoxb-SLACK-BOT-TOKEN

it returns the expected response:

{
    "ok": true,
    "channels": [
        {
...

So I'm not sure why I'm the only one having the issue, but maybe it's because I created my app on the Slack Api portal yesterday and it uses this new header auth style?

If that's the case, then it looks this library needs to be updated to pass the token in the Authorization header for new Slack Apps.

Edit: Here's the changelog where they deprecated querystring authentication: https://api.slack.com/changelog/2020-11-no-more-tokens-in-querystrings-for-newly-created-apps

Ubuntu 18.04.03, Swift 5.0.2, SlackKit "upToNextMinor 4.3.0"

Build silently fails, final output from swift build --verbose is like this:

/usr/bin/clang -target x86_64-unknown-linux --sysroot / -fPIC -g -O0 -DSWIFT_PACKAGE=1 -DDEBUG=1 -fblocks -fmodules -fmodule-name=CNIOOpenSSL -I /home/pseudo/gaijinbot/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/include -fmodule-map-file=/home/pseudo/gaijinbot/.build/checkouts/swift-nio-ssl-support/module.modulemap -fmodules-cache-path=/home/pseudo/gaijinbot/.build/x86_64-unknown-linux/debug/ModuleCache -MD -MT dependencies -MF /home/pseudo/gaijinbot/.build/x86_64-unknown-linux/debug/CNIOOpenSSL.build/shims.c.d -c /home/pseudo/gaijinbot/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/shims.c -o /home/pseudo/gaijinbot/.build/x86_64-unknown-linux/debug/CNIOOpenSSL.build/shims.c.o :

. $

I try install this framework via Cocoapods for iOS application. But can not import be cause of error:

Showing Recent Messages :-1: framework not found SlackKit

Much like sendMessage has sendThreadedMessage. There is currently no way to respond in a thread with an ephemeral message.

Alternatively, networkInterface could be exposed or another extension point could be added for library consumers, such as an "additionalParameters" function parameter that would allow passing in additional fields to help build the payload.

Or perhaps there's something else I missed that might allow us to do this?

After dependencies update a few days ago I've got the error:

Type 'SlackKit' does not conform to protocol 'RTMAdapter'

Error repeats even after fresh install. Adding a stub for connectionClosed(with error: Error, instance: SKRTMAPI) method fixes the problem, but not sure that this is the proper solution (: Looks

Is it only my problem or there some bug of SlackKit conformance to SKRTMAPI? Thanks in advance!

Attempts to build recent versions of SlackKit fail when using SPM.

Using the following steps, building an application including SlackKit fails when specifying version 4.2.0 rather than 4.1.0 (which still works):

mkdir x6
cd x6
swift package init --type executable

edit Package.swift to include dependencies

swift package generate-xcodeproj
open x6.xcodeproj

build project using Xcode UI

$ swift --version
Apple Swift version 4.2.1 (swiftlang-1000.11.42 clang-1000.11.45.1)
Target: x86_64-apple-darwin18.2.0

Xcode Version 10.1 (10B61)

Build errors are in dependencies of packages required by SlackKit. e.g.

... x6/.build/checkouts/swift-nio-ssl.git--5028798909648298346/Sources/CNIOOpenSSL/include/c_nio_openssl.h:17:10: fatal error: 'openssl/conf.h' file not found
#include <openssl/conf.h>
         ^~~~~~~~~~~~~~~~
1 error generated.

I see this problem on both of my systems. Hopefully this isn't an embarrassing pilot error on my behalf.

slackkit.bug.txt