Magento2: bin/magento throws a Warning: array_key_exists(): The first argument should be either a string or an integer

[diazwatson]

Preconditions (*)

1. Checkuot commit e008e80c6ee in 2.3-develop branch
2. PHP 7.1.26

Steps to reproduce (*)

1. Run bin/magento

Expected result (*)

1. See a list of all commands available

Actual result (*)

Warning: array_key_exists(): The first argument should be either a string or an integer in magento/vendor/zendframework/zend-eventmanager/src/SharedEventManager.php on line 153

[m2-assistant[bot]]

Hi @diazwatson. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [x] Summary of the issue
• [x] Information on your environment
• [x] Steps to reproduce
• [x] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@diazwatson do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[diazwatson]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @diazwatson. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @diazwatson, here is your Magento instance.
Admin access: https://i-23993-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[diazwatson]

Forgot there is not ssh access to this instance so it is not possible to reproduce the issue there 🤷‍♂

[diazwatson]

I have re tested this after fetching the latest changes in 2.3-develop branch and don't see the issue

[devamitbera]

I have faced the same issue and i have update my repo with the last 2.3-develop.

After that, I run composer update and my issue is resolved.

[rav-redchamps]

I had faced the same problem in 2.4-develop. As shared by @devamitbera, running composer updatesolves the error.

[hiteshgb]

Any update on this issue as I am also facing same issue.

[diazwatson]

hi @hiteshgb have you tried after running composer update ?

[hiteshgb]

Yes but after after removing updates it is still showing error.