Laravel Abort and Exceptions adding debug/stack trace to API response | APP_DEBUG=FALSE

If I throw an exception in my API controllers/routes it always returns an object including the stack trace. I have set APP_DEBUG=FALSE and APP_ENV=production yet I always get a stack trace like below…

Say I throw any one of these in a controllers method:

throw new HttpException(410, 'Http Exception is gettting a stack trace.');

abort(404, 'Please tell me debug is not found!');

throw new UpdateResourceFailedException('Even my custom exception! How?', 422);

It returns an object like this:

{
"message": "Message",
"status_code": 410,
"debug": {
"line": 412,
"file": "/var/www/example.com/app/Http/Controllers/OrderController.php",
"class": "Symfony\Component\HttpKernel\Exception\HttpException",
"trace": [
"#0 [internal function]: App\Http\Controllers\OrderController->show()",
"#1 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(55): call_user_func_array()",
"#2 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(44): Illuminate\Routing\Controller->callAction()",
"#3 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Route.php(203): Illuminate\Routing\ControllerDispatcher->dispatch()",
"#4 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Route.php(160): Illuminate\Routing\Route->runController()",
"#5 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(572): Illuminate\Routing\Route->run()",
"#6 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Routing\Router->Illuminate\Routing\{closure}()",
"#7 /var/www/example.com/vendor/dingo/api/src/Http/Middleware/Auth.php(55): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}()",
"#8 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Dingo\Api\Http\Middleware\Auth->handle()",
"#9 /var/www/example.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()"...

I can’t turn it off or figure out why it’s adding it. Any help would be appreciated. Yes, I have dumped my .env variables and my config file to see what the system thinks the value is and invariably it’s: "debug":false

Any ideas on why this is returning debug?

from Newest questions tagged laravel-5 – Stack Overflow https://ift.tt/35mRvbl
via IFTTT

Related Posts

Codeigniter : Parse error: syntax error, unexpected ‘const’ (T_CONST), expecting variable (T_VARIABLE) in Laravel project

I’m getting following error: **Parse error: syntax error, unexpected ‘const’ (T_CONST), expecting variable (T_VARIABLE)** Note : It’s working in local but facing issue in production server. private…

Firebase receive notification while tab is active or on focus

What i want is to be able to perform an action when a user receives a notification while the browser is open and tab is active or…

Laravel’s alias loader does not find class

We have a legacy project that we cannot update and we need to make some changes in symfony’s Response.php in vendor. We have solved this by copying…

Laravel 5 – generic document management

I have a system where you can create different types of unique documents. For instance, one document is called Project Identified and this expects certain inputs. Originally,…

Laravel Nova limit the results in indexQuery

I ran intro a situation where I need to limit the results of a resource to only 3 results. To be more specific, based on the logged…

Auditoria en laravel 5.8 [closed]

Cómo puedo automatizar el registro de actividades de un usuario en laravel? Si un usuario ingresa a un app de laravel, debo guardar toda su actividas, a…

Leave a Reply

Your email address will not be published.