Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invisible \u00A0 character before is_object() call #380

Open
chriswayoub opened this issue Oct 22, 2019 · 5 comments
Open

Invisible \u00A0 character before is_object() call #380

chriswayoub opened this issue Oct 22, 2019 · 5 comments

Comments

@chriswayoub
Copy link

There are non-breaking space UTF-8 characters in the source code that cause fatal errors. It looks like this is the case everywhere that the code calls is_object when checking the $data array. I've referenced one example below, but they all have the same issue.

if(is_array($data) || is_object($data)) {

The fatal error that is thrown is:

Call to undefined function net\authorize\api\contract\v1\ is_object()

This looks like an issue with the code generation script:

if(is_array($data) || is_object($data)) {

According to the contribution guide, I can't submit a pull request for those files.

@jimfurnier
Copy link

Same issue, any solutions, other than temporarily updating the vendor code?

@zohaibhassan156
Copy link

Same issue,

In GetTransactionDetailsResponse.php line 96:

Call to undefined function net\authorize\api\contract\v1\Â is_object()

@jmcguire81
Copy link

I am seeing the same hidden character issue here. AuthNet, any updates on this? We are looking at upgrading our AIM implementation to make use of this library through Composer, but this obviously won't fly for production.

if(is_array($data) || is_object($data)) {

@packytagliaferro
Copy link

Is there any news on this?? I get this from the sample code

@schmich
Copy link

schmich commented May 24, 2021

@gnongsie It looks like this issue (and #390) were addressed in your commit 4daeec2. Additionally, it looks like this commit was part of the 2.0.2 release.

Is my understanding correct? If so, it looks like these two issues have been fixed and can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants