Bugsnag Ignoring Environment about bugsnag-laravel

[jaketoolson]

I believe bugsnag release-stages do not have anything to do with any environments created/identified in Laravel. You have to map them to each other.

For example:

// Current laravel environment
$env = strtolower(app()->env);

// Match Laravel environments to bugsnag environments.
switch($env)
{
    case 'local' :
    case 'another-local' :
        case 'another-local-local':
        Bugsnag::setReleaseStage('local');
        break;

    case 'paas' :
    case 'development' :
        Bugsnag::setReleaseStage('development');
        break;

    case 'staging' :
        case 'staging-2' :
        Bugsnag::setReleaseStage('staging');
        break;

    case 'production' :
        Bugsnag::setReleaseStage('production');
        break;

    default :
        Bugsnag::setReleaseStage('production');
        break;
}

// Identify which bugsnag environments should be logged.
Bugsnag::setNotifyReleaseStages(array('production', 'staging'));

[jaketoolson]

Looking further, my example is a 1/2 truth I believe -- I have many environments (dont ask) and I map them to common ones.

[snmaynard]

It looks like we forgot to tag release 1.0.4 and that was the release that had the notifyreleasestages in. If you were using a tagged version can I suggest upgrading to 1.0.4 and trying again?

Apologies for that!

[chipbell4]

Thanks @snmaynard that did the trick! My composer.json was using "1.*" as the version so my current vendor folder had 1.0.3. Composer update bumped that up to 1.0.4, so I should be good now.
Thanks.

[snmaynard]

Great, glad that fixed it for you!