Botman 2.0 Facebook Messenger聊天机器人say()方法失效求助

Common Fixes to Try #

1. Explicitly Pass Context to say() #

Unlike reply() which uses the current conversation's built-in context, say() requires you to specify the recipient and driver explicitly—this is the most common culprit.

For Facebook Messenger, you need to pass the user's Page-Scoped ID (PSID) and the Facebook driver class when calling say(). Here's how to adjust your code:

$botman->hears('Hello BotMan!', function($bot) {
    $user = $bot->getUser();
    $bot->reply('Hello!');
    
    // Add explicit user ID and driver to say()
    $bot->say('This is a message via say()', $user->getId(), FacebookDriver::class);
    
    $bot->ask('Whats your name?', function($answer) use ($bot) {
        $bot->reply('Nice to meet you, ' . $answer->getText());
    });
});

Without this context, BotMan can't route the message correctly to Facebook's API.

2. Validate Webhook Endpoint Setup #

Even if your server receives requests, double-check that you're using BotMan's standard listen() method to handle both verification and message responses. Custom code before listen() might send an early 200 OK that breaks BotMan's processing flow.

Ensure your endpoint code looks like this:

use BotMan\BotMan\BotManFactory;
use BotMan\Drivers\Facebook\FacebookDriver;

$config = [
    'facebook' => [
        'token' => 'YOUR_PAGE_ACCESS_TOKEN',
        'app_secret' => 'YOUR_APP_SECRET',
        'verification' => 'YOUR_VERIFICATION_TOKEN',
    ]
];

$botman = BotManFactory::create($config);

// Your hear/ask commands go here

$botman->listen();

3. Check Facebook API Permissions & Limits #

Just because reply() works doesn't mean say() won't hit restrictions:

• Confirm your Page Access Token has the pages_messaging permission enabled in the Facebook App Dashboard
• Check for rate limit alerts in the dashboard—Facebook restricts outgoing messages to prevent spam
• Verify the user hasn't blocked your page or opted out of messaging

4. Enable Debug Mode to Diagnose Requests #

Turn on BotMan's debug mode to see exactly what's being sent to Facebook's API. Add this to your config:

$config = [
    'facebook' => [
        // Your existing Facebook config
    ],
    'botman' => [
        'debug' => true,
    ]
];

Check your server logs for outgoing request errors—messages like "Invalid Recipient" or "Unauthorized" will point directly to issues with user IDs or access tokens.

5. Confirm Driver Version Compatibility #

BotMan 2.0 requires specific driver versions. Ensure your composer.json has the compatible Facebook driver:

{
    "require": {
        "botman/driver-facebook": "~1.0"
    }
}

Run composer update to sync dependencies and rule out version mismatches.

内容的提问来源于stack exchange，提问作者henrique romao