[Cannot cast value of type NULL to type string error in Inline mode] about telebot HOT 6 CLOSED

Dublicate of #59. I tested inline mode and it works well, attaching script below. Again - your description is unclear. You are only telling that something is not working, but not providing code examples and full error trace. I'm not responsible for mistakes you make in your project.

<?php

use WeStacks\TeleBot\Objects\Update;
use WeStacks\TeleBot\TeleBot;

require_once 'vendor/autoload.php';

$bot = new TeleBot([
    'token' => '<token>'
]);

$bot->addHandler(function (TeleBot $bot, Update $update, callable $next) {
    if (!isset($update->inline_query)) {
        return $next();
    }

    return $bot->answerInlineQuery([
        'inline_query_id' => $update->inline_query->id,
        'results' => [[
            'type' => 'article',
            'id' => 'google',
            'title' => 'Google',
            'url' => 'http://google.com/',
            'input_message_content' => [
                'message_text' => $update->inline_query->query
            ]
        ]]
    ]);
});

$last_offset = 0;
while (true) {
    $updates = $bot->getUpdates([
        'offset' => $last_offset + 1
    ]);
    foreach ($updates as $update) {
        $bot->handleUpdate($update);
        $last_offset = $update->update_id;
    }
}

from telebot.

This is a test and in the file SearchMoviesInlineQuery.php
You can see is a very simple handler
But the update doesn't reach the handler and it exits in Type.php:96 because $value_type is equal to NULL

from telebot.

I've just cloned your project, and everything works as intended.

from telebot.

I really don't understand that it works properly in long polling mode

But it gives an error in the webhook

from telebot.

I figured it out. It is actually a bug. There is a weird behavior in Telegram's API: when the incoming update is inline query, there is a field - inline_query.offset. Documentation says that this field is actually a string, however - when you receive updates using long polling, it sends an empty string, as docs say. But when they send a webhook request - they send NULL, that is not passing validation in our library. It's kind of weird, but I guess we can write some "crutches" to expect this from webhooks.

UPD. Actually, by second though, it's not Telegram's API, but Laravel's middleware, that converts empty strings to NULL on every request. It's even easier to fix then. For quick fix: enter app/Http/Kernel.php and remove ConvertEmptyStringsToNull middleware from your global middleware list. In the next update, I'll write the webhook route in a way to bypass Laravel's global middleware

protected $middleware = [
    // \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class,
];

from telebot.

ok thank you

from telebot.