Apigility Resource Id already exists in ACL.

[adear11]

Let me preface by saying I'm not 100% sure if this is an Apigility issue or a zf-mvc-auth issue.

I have an Apigility powered API currently running Apigility 1.4. I just did a composer update to update all my dependencies. After doing the update, when I try to hit my api, I get an exception that says:

Fatal error: Uncaught Zend\Permissions\Acl\Exception\InvalidArgumentException: Resource id 'MyAPI\V1\Rest\Questions\Controller::collection' already exists in the ACL in /Users/adear11/Documents/localDevelopment/api.mysite.com/vendor/zendframework/zend-servicemanager/src/ServiceManager.php on line 765

Zend\ServiceManager\Exception\ServiceNotCreatedException: Service with name "ZF\MvcAuth\Authorization\AclAuthorization" could not be created. Reason: Resource id 'MyAPI\V1\Rest\Questions\Controller::collection' already exists in the ACL in /Users/adear11/Documents/localDevelopment/api.mysite.com/vendor/zendframework/zend-servicemanager/src/ServiceManager.php on line 765

After doing some testing, I found that if I pinned zf-campus/zf-mvc-auth to 1.4.2 in my composer.json file instead of letting it update to 1.4.3 my api and Apigility works as expected.

It is worth noting that this API was originally built using Apigility with Apigility <1.0 (0.9.1 if I remember correctly).

I'm happy to provide any information that may be needed. If this would be better served being posted to the Apigility project's issue tracker I'll be happy to close this and move there. I just thought that since I've narrowed down the problem the this package specifically, this might be the appropriate place.

[weierophinney]

This repository has been closed and moved to laminas-api-tools/api-tools-mvc-auth; a new issue has been opened at laminas-api-tools/api-tools-mvc-auth#3.