getting encoding message issue when sent ordinary text

[hbakhtiyor]

when i sent Ooops, something went wrong!, it displays Ooops, something went wrong%21
the ! char encoded to %21

how to resolve it?

[peterswimm]

Can you post a snippet of your code?

[hbakhtiyor]

i used the sample using with replyPrivateDelayed & replyPublicDelayed

[peterswimm]

And you didnt edit any code? Did you follow the instructions as he posted on the medium article?
https://api.slack.com/tutorials/easy-peasy-slash-commands

My guess without seeing your project that either you copy pasted some bad code, or missed a step.

[hbakhtiyor]

hmm, just use Delayed version, you'll reproduce it, I properly followed and configured!

[hbakhtiyor]

@peterswimm did you try it?

[peterswimm]

@hbakhtiyor I did not! You might also try posting the question in our deve community if you are 100% sure about your code and Slack side setup:

https://community.botkit.ai/

[0xceb1d]

Any more on this? Having encoding issues with Slack and the / character.
1/1 becomes 1/1

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[hbakhtiyor]

up

[adantoscano]

Have you tried with this #240 ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cooperka]

The issue description here is ambiguous, but I'm encountering this when sending messages from the bot. Some random outgoing messages will be url-encoded, with normal characters like apostrophe coming out as '.

My workaround is to use a send middleware to decode:

import { decode } from 'he';

controller.middleware.send.use((bot, message, next) => {
  // Decode outgoing messages to make sure there are no weird URI encoded characters.
  // Encoding happens automatically sometimes for unknown reasons.
  message.text = decode(message.text);

  next();
});

Note: These issues occur with the Twilio adapter, but the Emulator works fine.