sentry:test command sometimes works sometimes doesn't about sentry-laravel HOT 9 OPEN

This seems like it might be an networking issue. I would advise you to do two things.

First, upgrade to the latest 4.x release of the SDK (changes are minimal in most cases but do please look over the upgrade guide!)

Seconds, if that doesn't solve the issue you can use the new logger option to get some more output that might show where the errors lies, documentation for that here: https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/#logger

Let me know if either (or both) of those helps!

from sentry-laravel.

Hello, unfortunately the suggestions didn't help.
This is the whole situation that's happening:
After running php artisan sentry:publish --dsn= and accepting test event, the test event passes without errors. For some time after that when I run php artisan sentry:test the event is sent without issues. Again after some time it start giving errors but not every time until it gets to stage where it fails every time.

from sentry-laravel.

This sounds super strange, is some external tool updating your .env file perhaps?

Or are you using config caching (you can try clearing it with php artisan config:clear)?

Unless the config is changing this makes no sense to me 😅

from sentry-laravel.

Hey, I've got a similar problem, just that sentry now stopped working.
The error message is also not very helpful

 sail artisan sentry:test
DSN discovered from Laravel config or `.env` file!
Sending test event...
There was an error sending the event.
Please check if your DSN is set properly in your `.env` as `SENTRY_LARAVEL_DSN` or in your config file `config/sentry.php`.

DSN is properly set. And it is also working. I used the same DSN for testing for the javascript integrations and javascript errors were properly captured.

But any laravel errors / exceptions are not captured.
I've migrated from 3 -> 4, then it stopped working.

Have the latest sentry-laravel version.
I have also deleted config/sentry.php and re-ran the artisan command.

from sentry-laravel.

Same suggestions for you to try: https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/#logger. Create a config/sentry.php with:

<?php

return [
    'logger' => new \Sentry\Logger\DebugFileLogger(filePath: storage_path('logs/sentry.log')),
];

Do not use config caching with this since that doesn't work :)

Anything interesting in the output?

from sentry-laravel.

I have the same problem. This is the result in sentry.log:

from sentry-laravel.

I'm sorry for not responding. I decided to go with the bug and I'm not having any issues reporting errors to sentry.
My guess is that this is some kind of a problem with sentry:test command for v4 since it's all working fine on server using integration class Integration::captureUnhandledException($exception);.

from sentry-laravel.