bugsnag / bugsnag-laravel

BugSnag notifier for the Laravel PHP framework. Monitor and report Laravel errors.
https://docs.bugsnag.com/platforms/php/laravel/
MIT License
876 stars 129 forks source link

Call to undefined method Bugsnag\Configuration::getRedactedKeys() #435

Closed WebMedic-X closed 3 years ago

WebMedic-X commented 3 years ago

Describe the bug

Not sure why recently stopped receiving Bugsnag reports and then checked the logs and found this error message showing up:

Uncaught Error: Call to undefined method Bugsnag\Configuration::getRedactedKeys() in public_html/vendor/bugsnag/bugsnag/src/Report.php:798

Environment

imjoehaines commented 3 years ago

Hey @WebMedic-X

It looks like your install of bugsnag-php has been corrupted somehow — the Report class is clearly from v3.26.0 as that version introduced the call to getRedactedKeys, but the Configuration class can’t be v3.26.0 as it’s missing the getRedactedKeys method

Can you let us know how you updated to bugsnag-laravel v2.22.0 and bugsnag-php v3.26.0?

Could you also run the following commands to show the state of your Bugsnag packages:

  1. composer show 'bugsnag/*'

    
This should output
:

    
bugsnag/bugsnag            v3.26.0 Official Bugsnag notifier for PHP applications.
    bugsnag/bugsnag-laravel    v2.22.0 Official Bugsnag notifier for Laravel applications.
    bugsnag/bugsnag-psr-logger v1.4.3  Official Bugsnag PHP PSR Logger.
  2. grep "'version' " vendor/bugsnag/bugsnag/src/Configuration.php

    This should output:

            'version' => '3.26.0',
  3. tail vendor/bugsnag/bugsnag/src/Configuration.php

    This should output:

        /**
         * Get the array of metadata keys that should be redacted.
         *
         * @var string[]
         */
        public function getRedactedKeys()
        {
            return $this->redactedKeys;
        }
    }

If any the above commands show different output, it's likely something has gone wrong when updating bugsnag-php to v3.26.0

Running composer update 'bugsnag/*' should fix the issue by ensuring bugsnag-php v3.26.0 is properly installed. If Composer doesn't think there's anything to update, try deleting vendor/bugsnag and rerunning that command to force Composer to reinstall the Bugsnag packages from scratch

WebMedic-X commented 3 years ago

Hi @xander-jones

Interestingly, all the commands report exactly what you showed but it was still showing that error

Deleted vendor/bugsnag and re-installed it and I think that solved it

Thank you!

xljones commented 3 years ago

I have to give props to @imjoehaines for solving this one 👏 , I only added the label 😁 , but thank you for letting us know that this is now resolved!