Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

zaster's avatar

Class 'Arcanedev\LogViewer\LogViewerServiceProvider' not found

I need to get rid of this

Class 'Arcanedev\LogViewer\LogViewerServiceProvider' not found

error.

I am unable to visit my website in the production.

Managed to avoid this error by taking out the package from the composer.json file etc...(Local Environment)

But same thing didn't work on the production

tried

php artisan config:cache
composer dump-autoload

and still struggling.

0 likes
5 replies
Tippin's avatar

@zaster You may need to manually go into your bootstrap/cache folder and remove the files inside. Then rerun config:cache, route cache if you use that, etc

config.php
packages.php
services.php

You may also need to remove that from your config/app.php if you placed that line under your providers

zaster's avatar

@tippin

i tried that , but still no result(Trying more....). I think it is something to do with the cache or something similar to that , because no issue in the local environment.

I am unable to run any artisan commands in the production due to this error

zaster's avatar
zaster
OP
Best Answer
Level 9

@tippin

Solved the issue after completely removing all files and reinstalling from the beginning through version control

1 like
asifarham44's avatar

The error Class 'Arcanedev\LogViewer\LogViewerServiceProvider' not found usually occurs when the Laravel LogViewer package is not installed correctly, has been removed, or the service provider is still registered after the package was uninstalled. To resolve it, ensure the package is installed via Composer by running composer install or composer require arcanedev/log-viewer, and verify that the service provider registration matches the installed version. If you no longer use the package, remove Arcanedev\LogViewer\LogViewerServiceProvider::class from your configuration files and clear Laravel caches using php artisan config:clear, php artisan cache:clear, and composer dump-autoload. Checking your package dependencies and application configuration should resolve the issue.

Please or to participate in this conversation.