Log Viewer 500 Error Despite Assets Being Published

[NgYueHong]

I've been using the Log Viewer in my Laravel project for several months without any issues. However, recently I encountered a 500 Internal Server Error when trying to access the Log Viewer interface.

Upon inspecting the log file, I found the following error:

ERROR: Log Viewer assets are not published. Please run: php artisan vendor:publish --tag=log-viewer-assets --force
{"userId":1,"exception":"[object] (RuntimeException(code: 0): Log Viewer assets are not published. Please run: php artisan vendor:publish --tag=log-viewer-assets --force at /home/laravelweb/system/vendor/opcodesio/log-viewer/src/LogViewerService.php:352)"}

I verified that the front-end assets are indeed present in the public/vendor directory. I also re-ran the suggested command:
php artisan vendor:publish --tag=log-viewer-assets --force

Despite this, the error persists and the Log Viewer still returns a 500 error.

What could be causing this issue, even though the assets are already published? How can I resolve this error and restore access to the Log Viewer?

[serious-angel]

Considering the source, it checks for the following file. Does the file exist?:

log-viewer/src/LogViewerService.php

Lines 349 to 353 in 503c545

	$publishedPath = public_path('vendor/log-viewer/mix-manifest.json');
	if (! File::exists($publishedPath)) {
	throw new \RuntimeException('Log Viewer assets are not published. Please run: php artisan vendor:publish --tag=log-viewer-assets --force');
	}

[NgYueHong]

Thank you very much for helping. I found the problem already. The problem is caused by my public_path setting is wrong.

[arukompas]

Hey @NgYueHong @serious-angel , looks like the issue is similar to #463

The assetsAreCurrent() method did not respect the configured custom asset path.

• Fixed in Fix assetsAreCurrent to respect assets_path config #483
• Release tagged - v3.21.1