Unresolvable Dependency in Rollbar\RollbarLogger Since v8.1.0

[closca]

Since upgrading to version 8.1.0, we have started receiving the following error:

Unresolvable dependency resolving [Parameter #0 [ <required> array $config ]] in class Rollbar\RollbarLogger {"exception":"[object] (Illuminate\Contracts\Container\BindingResolutionException(code: 0): Unresolvable dependency resolving [Parameter #0 [ <required> array $config ]] in class Rollbar\RollbarLogger at

This occurs even though Rollbar is not enabled in our configuration or .env file.

Expected Behavior

• The application should not attempt to instantiate Rollbar\RollbarLogger since Rollbar is disabled.
• No dependency resolution errors related to Rollbar should occur.

Actual Behavior

• The application throws an unresolvable dependency error related to Rollbar\RollbarLogger.
• This issue started occurring only after updating to v8.1.0.
• There are no explicit calls to Rollbar\RollbarLogger in our code.

Steps to Reproduce

1. Upgrade to Rollbar v8.1.0.
2. Ensure that Rollbar is not enabled in the configuration.
3. Run the application.
4. Observe the error in the logs.

Additional Context

• This issue did not occur in previous versions.
• It seems like Rollbar is being instantiated even when not configured.
• The application was functioning as expected before the upgrade.

Would appreciate any guidance on resolving this issue! 🚀

[linear]

SDK-449 Unresolvable Dependency in Rollbar\RollbarLogger Since v8.1.0

[mantas-done]

I ran into the same issue with Rollbar v8.1. If your .env file has an empty token (ROLLBAR_TOKEN=), you’ll see this error, which can be helpful in development. Adding a valid token (e.g. ROLLBAR_TOKEN=12345678901234567890123456789012) fixes the problem.

[JerryVerhoef]

When you specify a bogus Token will that mean that Rollbar is always initialized ? And sending logs from dev and test environment to Rollbar?

I don't think that Rollbar is very happy with this situation?

[nepda]

It's because the new \Rollbar\Laravel\RollbarServiceProvider::boot method has the \Rollbar\RollbarLogger in it's signature and Laravel will try to resolve the \Rollbar\RollbarLogger even if Rollbar is not configured and the stop method would return true.

[danielmorell]

We released a fix for this from @JerryVerhoef in v8.1.1 just now. Thanks for your patience and assistance!