- How do I install the BotMan Kik driver with Composer?
- Install it with composer require botman/driver-kik alongside botman/botman. Release 1.1.0 adds Laravel service providers, so on Laravel 5.5 and newer the provider should be picked up by package auto-discovery without editing config/app.php. Run php artisan package:discover if discovery has not already run, then configure your Kik credentials before handling traffic.
- Which Laravel and PHP versions does botman/driver-kik support?
- Check the require constraints in the package composer.json for the exact Laravel and PHP matrix, because 1.1.0 is documented primarily through its release notes. Laravel applications on 9 through 11 that rely on package discovery are the most natural fit. Lumen, Laravel versions before 5.5, and plain PHP setups need manual registration instead of auto-discovery.
- Do I need to register the Kik driver service provider manually in config/app.php?
- Usually no. If the package declares its providers under extra.laravel.providers, discovery registers them automatically on Laravel 5.5 and above. If you upgraded from 1.0.x and already had manual entries or hand-rolled bindings, remove them to avoid double registration. For Lumen, register the provider explicitly in bootstrap/app.php.
- How do I configure Kik credentials and receive incoming messages?
- Supply your Kik bot username and API key through the published BotMan configuration, then point the Kik bot webhook at a route that hands the request to BotMan. BotMan normalizes the incoming payload, so your hears and conversation handlers fire exactly as they do on other channels. Clear and rebuild cached config after changing credentials so the new values take effect.
- Does the Kik driver support BotMan hears, conversations, and middleware?
- Yes. The driver translates Kik messages into BotMan's standard message objects, so hears patterns, conversation flows, and middleware all work unchanged. That means the same handler code can serve Kik and any other BotMan channel you enable. Only the channel-specific setup and credentials differ per driver.
- Can I use botman/driver-kik without Laravel in a plain PHP application?
- The service providers added in 1.1.0 are meant to be additive, so the underlying driver should remain usable outside Laravel by instantiating it and loading your Kik configuration directly. Confirm this against the package source for your installed version before committing to a non-Laravel deployment. If your app is Laravel-based, the provider path is the simpler route.
- How do I test a Kik bot built on BotMan without hitting the live Kik API?
- Keep your handlers thin and test them through BotMan's message abstraction rather than through real Kik traffic, so no API key or network call is required. Stub or mock the Kik driver where you need deterministic replies, and reserve genuine Kik webhook calls for a staging bot account. Also assert your route returns the expected responses when the payload shape changes.
- Why did my Kik bot stop responding after upgrading to 1.1.0?
- Start with the bootstrap layer: confirm the provider is discovered, check that no legacy manual registration remains, and rebuild the cached config with php artisan config:clear followed by config:cache. Version mismatch between Laravel and the package, or stale cached configuration, are the most common causes. If everything on your side checks out, verify the Kik Bot API is reachable and still accepts your credentials.
- Is the Kik Bot API still supported for this driver?
- Kik's bot platform has changed over time, so verify current API compatibility before relying on this driver in production. The package itself is a thin translation layer over BotMan, and its health depends on the upstream Kik endpoints staying available. Run a spike against a real bot account and pin a known-good version if you proceed.
- What are the alternatives to botman/driver-kik?
- If Kik is optional for you, BotMan offers drivers for Telegram, Facebook Messenger, Slack, Web, and other channels, plus a generic web driver for custom endpoints. Writing against BotMan's channel-agnostic API keeps your conversation logic portable, so adding or dropping Kik later is mostly a configuration change. A direct Kik SDK is only worth it if you need platform features BotMan does not expose.