net\authorize\api\contract\v1\CreateCustomerProfileFromTransactionResponse does not exist

[efitz16]

The file lib/net/authorize/api/controller/CreateCustomerProfileFromTransactionController.php uses the response type net\authorize\api\contract\v1\CreateCustomerProfileFromTransactionResponse, but a corresponding file does not exist in lib/net/authorize/api/contract/v1.

Changing the line $responseType = 'net\authorize\api\contract\v1\CreateCustomerProfileFromTransactionResponse'; to $responseType = 'net\authorize\api\contract\v1\CreateCustomerProfileResponse'; fixes the issue. I cannot submit a pull request for this file according to your contributors's guide.

I found this error by trying to implement the code found in your sample code. $controller = new AnetController\CreateCustomerProfileFromTransactionController($request); throws an error: Fatal error: Class 'net\authorize\api\contract\v1\CreateCustomerProfileFromTransactionResponse' not found. This was previously discussed in a closed issue.

Thank you.

[bearinaustin]

Bumping we are experiencing this same issue. We are freezing our updates for this package in composer and using the manual fix mentioned https://github.com/AuthorizeNet/sdk-php/issues/105 as a temporary workaround..

Wondering when this will be made available in an approved branch??

[BFunk86]

So it is now November 2022 and this is still not fixed. Do they plan on ever fixing this? It has been an issue since February 2016. All they need to do is merge pull request #424

[gregorysandoval]

I agree with you 100%. But, as no one's been even assigned to this it's obvious the answer is no. Visa bought Authorize.Net (ain't de-regulation grand?) and I'm quite sure it's the same old story. Buy company, lay off half of the legacy staff, and tasks like maintaining the SDK's or monitoring issues in the repo just aren't that important to the ownership company. Same thing happened with PayPal who recently just closed all the open issues on their SDK repos after letting the SDK languish on GitHub for years.

This sort of behavior is, in part, why my installs have not been updated to PHP 8.x and I'm holding out as long as I can because I know there will be issues and no support for them. You have to be a realist - this is modern business.

[gnongsie]

This has been corrected in the latest version.
Closing this issue based on that.