-
Notifications
You must be signed in to change notification settings - Fork 50
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
Fatal error when php_uname()
is disabled for security reasons.
#115
Comments
@jessdelacruzsantos This issue has been addressed and resolved in the recent release of |
hi @iamdharmesh These changes should be brought in and reflect in our July release. Currently we scheduling for that to go live July 6th. Thanks again for your contributions in highlighting this issue! |
@zenmasterjobo is there any update on the release? |
hi @Sidsector9 and @iamdharmesh Version 29.0.0.20230720 incorporates APIMatic's core change Please check it out and let me know if your problem is still persisting! |
Thanks @zenmasterjobo , I just confirmed that the issue is no longer present. |
@Sidsector9 Excellent! Thanks again for reporting the issue! |
Describe the bug
There are many web hosting providers that disable a number of built-in PHP functions due to security reasons. When the
php_uname()
function is disabled on a web host SDK throws the fatal error.Expected behavior
Square SDK should work fine without any fatal error if php_uname is disabled.
To Reproduce
Steps to reproduce the bug:
SquareClient
. You will get the fatal error.Screenshots
If applicable, add screenshots to help explain the bug.
Square SDK version
24.0.0.20221116
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: