After closing reply keyboard can't to open it again
Opened this issue · 18 comments
Deleted user commented
toJSON: [Function: responseToJSON], caseless: Caseless { dict: [Object] }, body: { ok: false, error_code: 400, description: 'Bad Request: field "keyboard" of the ReplyKeyboardMarkup should be an Array' } } }
That's the last lines from long console outputting
alexandercerutti commented
Hi @furmanServices, I don't know how to help you sincerely. If I don't see the code that caused that error, I cannot help you. Could you provide it please?
Deleted user commented
Yes, sure. With your library I also use node-telegram-bot-api. So, this
part of code closes the initialized previously reply keyboard:
// 🔴 Cancel request
bot.onText(/\/cancel/, async msg => {
const {
chat: { id }
} = msg
try {
let sessionData = JSON.parse(await session.getAsync(`users:${id}`))
if (sessionData) {
await session.delAsync(`users:${id}`)
let requestId = sessionData.data.requestId
if (requestId) {
await makeRequest("delete", "/api/requests", requestId)
}
}
await bot.sendMessage(id, papyrus.declinedRequest, rk.close())
rk.reset()
} catch (err) {
console.log(err)
logger.log(`error`, papyrus.errors.declineSection)
}
})
And after /cancel opertation I try to init new session with /start:
// 🏁 Start
bot.onText(/\/start/, async msg => {
const {
chat: { id, first_name, last_name, username }
} = msg
try {
await session.setAsync(
`users:${id}`,
JSON.stringify({
ctx: `initial`,
data: {
name: first_name,
lastName: last_name,
username,
phoneNumber: null,
chatId: id
}
})
)
await bot.sendMessage(id, papyrus.greeting, rk.open({ resize_keyboard:
true }))
} catch (err) {
console.log(err)
logger.log(`error`, papyrus.errors.startection)
}
})
…On Fri, 11 Jan 2019 at 15:30, Alexander Cerutti ***@***.***> wrote:
Hi @furmanServices <https://github.com/furmanServices>, I don't know how
to help you sincerely. If I don't see the code that caused that error, I
cannot help you. Could you provide it please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44or9YWWow-A6mbaNnpE8AUZobGqNJks5vCJHZgaJpZM4Z7dBj>
.
Deleted user commented
First time start works fine, but all the subsequent causes an issue I left
there.
On Fri, 11 Jan 2019 at 15:32, Andrey Furman <furman.services@gmail.com>
wrote:
… Yes, sure. With your library I also use node-telegram-bot-api. So, this
part of code closes the initialized previously reply keyboard:
// 🔴 Cancel request
bot.onText(/\/cancel/, async msg => {
const {
chat: { id }
} = msg
try {
let sessionData = JSON.parse(await session.getAsync(`users:${id}`))
if (sessionData) {
await session.delAsync(`users:${id}`)
let requestId = sessionData.data.requestId
if (requestId) {
await makeRequest("delete", "/api/requests", requestId)
}
}
await bot.sendMessage(id, papyrus.declinedRequest, rk.close())
rk.reset()
} catch (err) {
console.log(err)
logger.log(`error`, papyrus.errors.declineSection)
}
})
And after /cancel opertation I try to init new session with /start:
// 🏁 Start
bot.onText(/\/start/, async msg => {
const {
chat: { id, first_name, last_name, username }
} = msg
try {
await session.setAsync(
`users:${id}`,
JSON.stringify({
ctx: `initial`,
data: {
name: first_name,
lastName: last_name,
username,
phoneNumber: null,
chatId: id
}
})
)
await bot.sendMessage(id, papyrus.greeting, rk.open({ resize_keyboard:
true }))
} catch (err) {
console.log(err)
logger.log(`error`, papyrus.errors.startection)
}
})
On Fri, 11 Jan 2019 at 15:30, Alexander Cerutti ***@***.***>
wrote:
> Hi @furmanServices <https://github.com/furmanServices>, I don't know how
> to help you sincerely. If I don't see the code that caused that error, I
> cannot help you. Could you provide it please?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Ar44or9YWWow-A6mbaNnpE8AUZobGqNJks5vCJHZgaJpZM4Z7dBj>
> .
>
alexandercerutti commented
If you call rk.reset() you wipe out the whole keyboard content.
You don't have to call it if you want to reuse it.
Sincerely, I don't even know the reason I inserted .reset() as a method.
Deleted user commented
The thing is I add new row on /start command
// 🏁 Start
bot.onText(/\/start/, async msg => {
rk.addRow(keyboards.initial)
const {
Then if I close keyboard on /cancel, I'll receive 2 and more buttons
duplicated on each time /start called.
I've tried different ways: rk.reset(), rk.close() and both combinations.
Nothing works.
…On Fri, 11 Jan 2019 at 15:38, Alexander Cerutti ***@***.***> wrote:
If you call rk.reset() you wipe out the whole keyboard content.
You have to call rk.close() if you want to reuse it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44oq5f9D_cUFjkqhcYRWmPskqwjvc9ks5vCJPogaJpZM4Z7dBj>
.
alexandercerutti commented
I suggest you to create and populate the keyboards globally, or at least in you module, to have a static reference to them.
let rk1 = new ReplyKeyboard();
rk1.addRow(keyboards.initial);
bot.onText(/\/start/, async msg => { ... });
bot.onText(/\/cancel/, async msg => { ... });Anyway in the first chunk of code you showed me, you are not adding new rows.
Deleted user commented
Yes, rk is declared globally. In the first chunk, I showed you I mistakenly
removed the row with rk row adding.
Here's the full file for the vision completeness.
https://github.com/furmanServices/biz-bot/blob/master/src/app.js
…On Fri, 11 Jan 2019 at 15:52, Alexander Cerutti ***@***.***> wrote:
I suggest you to create and populate the keyboards globally, or at least
in you module, to have a static reference to them.
let rk1 = new ReplyKeyboard();rk1.addRow(keyboards.initial);
bot.onText(/\/start/, async msg => { ... });bot.onText(/\/cancel/, async msg => { ... });
Anyway in the first chunk of code you showed me, you are not adding new
rows.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44oglo6d6WG1FzxChnsakzaW_FYrtnks5vCJcjgaJpZM4Z7dBj>
.
alexandercerutti commented
Yeah okay, so initialize the keyboard once for all globally and just use it in your "bot.sendMessage".
Deleted user commented
I even tried to act in a such way:
http://joxi.ru/12Ml67YiMzOEQm
the same issue.
…On Fri, 11 Jan 2019 at 16:12, Alexander Cerutti ***@***.***> wrote:
Yeah okay, so initialize the keyboard once for all globally and just use
it in your "bot.sendMessage"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44oiQhZtcFsk8lj6PRO3iUpW01vipzks5vCJuvgaJpZM4Z7dBj>
.
Deleted user commented
Anyway, thanks for quick response.
On Fri, 11 Jan 2019 at 16:18, Andrey Furman <furman.services@gmail.com>
wrote:
… I even tried to act in a such way:
http://joxi.ru/12Ml67YiMzOEQm
the same issue.
On Fri, 11 Jan 2019 at 16:12, Alexander Cerutti ***@***.***>
wrote:
> Yeah okay, so initialize the keyboard once for all globally and just use
> it in your "bot.sendMessage"
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Ar44oiQhZtcFsk8lj6PRO3iUpW01vipzks5vCJuvgaJpZM4Z7dBj>
> .
>
alexandercerutti commented
I even tried to act in a such way: http://joxi.ru/12Ml67YiMzOEQm the same issue.
…
On Fri, 11 Jan 2019 at 16:12, Alexander Cerutti @.***> wrote: Yeah okay, so initialize the keyboard once for all globally and just use it in your "bot.sendMessage" — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/Ar44oiQhZtcFsk8lj6PRO3iUpW01vipzks5vCJuvgaJpZM4Z7dBj .
Have you tried, as I said, to initialize it globally?
Deleted user commented
rk is initialized globally in app.js. This file is an entry point of bot. I
dropped a link to you with the file to github repo. You may ensure by
yourself.
On Fri, 11 Jan 2019 at 16:25, Alexander Cerutti <notifications@github.com>
wrote:
… I even tried to act in a such way: http://joxi.ru/12Ml67YiMzOEQm the same
issue.
… <#m_5743807599634724196_>
On Fri, 11 Jan 2019 at 16:12, Alexander Cerutti ***@***.***> wrote: Yeah
okay, so initialize the keyboard once for all globally and just use it in
your "bot.sendMessage" — You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#2 (comment)
<#2 (comment)>>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ar44oiQhZtcFsk8lj6PRO3iUpW01vipzks5vCJuvgaJpZM4Z7dBj
.
Have you tried, as I said, to initialize it globally?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44onq_67qsXTYFOAnpbPlq9F9DYjgVks5vCJ7ugaJpZM4Z7dBj>
.
alexandercerutti commented
No, I meant to use .addRow() right below let rk = new ReplyKeyboard();
let rk = new ReplyKeyboard();
rk.addRow(keyboards.initial);
const bot = new TelegramBot(process.env.ACCELERATOR_TOKEN, {
webHook: {
port: process.env.ACCELERATOR_PORT
}
})
bot.setWebHook(`${process.env.ACCELERATOR_HOST}/bot${process.env.ACCELERATOR_TOKEN}`)
bot.on(`error`, err => logger.log(`error`, err))
bot.on(`webhook_error`, err => logger.log(`error`, err))
// 🏁 Start
bot.onText(/\/start/, async msg => {
const {
chat: { id, first_name, last_name, username }
} = msg
...Deleted user commented
But how to be in cases when we want to change keyboard dynamically, depends
on commands bot receives?
…On Fri, 11 Jan 2019 at 16:35, Alexander Cerutti ***@***.***> wrote:
No, I meant to use .addRow() right below let rk = new ReplyKeyboard();
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44onNf37L9O_h4B-iQ8fRARbRURA3wks5vCKEXgaJpZM4Z7dBj>
.
alexandercerutti commented
You can create multiple keyboards, one for case. You don't have to use only one necessarily.
Deleted user commented
It's way out. Thank for the time you dedicated for me.
Have a good evening.
Best regards, Andrey.
…On Fri, 11 Jan 2019 at 16:39, Alexander Cerutti ***@***.***> wrote:
You can create multiple keyboards, one for case. You don't have to use
only one necessarily.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44okm5SVpID2aGMQH9U25BPcpQnCXTks5vCKIKgaJpZM4Z7dBj>
.
alexandercerutti commented
You're welcome! Thank you for using my library! 😊
Deleted user commented
👍
…On Fri, Jan 11, 2019 at 16:42 Alexander Cerutti ***@***.***> wrote:
You're welcome! Thank you for using my library! 😊
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ar44otWDAp0uKqunzrHmNRmNQwkfhIX5ks5vCKK_gaJpZM4Z7dBj>
.