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

Still having issues with getting metrics.conversions_value #223

Closed
leandromayor opened this issue Oct 25, 2019 · 2 comments
Closed

Still having issues with getting metrics.conversions_value #223

leandromayor opened this issue Oct 25, 2019 · 2 comments
Assignees

Comments

@leandromayor
Copy link

Hi - It looks like it is related to JSON decoding so I believe you are running with REST transport? If it is the case, could you try enabling gRPC following the instruction in the requirements session of the getting started documentation and let us know if it fixes the problem?

Originally posted by @PierrickVoulet in #222 (comment)

I'm still having issues :/

Fatal error: Uncaught Exception: Expect float. in ../vendor/google/protobuf/src/Google/Protobuf/Internal/GPBUtil.php:182
Stack trace:
#0 ..vendor/google/protobuf/src/Google/Protobuf/DoubleValue.php(61): Google\Protobuf\Internal\GPBUtil::checkDouble(Object(Google\Protobuf\DoubleValue))
#1 ..vendor/google/protobuf/src/Google/Protobuf/Internal/Message.php(1009): Google\Protobuf\DoubleValue->setValue(Object(Google\Protobuf\DoubleValue))
#2 ..vendor/google/protobuf/src/Google/Protobuf/Internal/Message.php(79): Google\Protobuf\Internal\Message->mergeFromArray(Array)
#3 ../vendor/google/protobuf/src/Google/Protobuf/DoubleValue.php(38): Google\Protobuf\Internal\Message->__construct(Array)
#4 ../src/Google/Ads/GoogleAds/V1/Common/Metrics.php(184 in ../vendor/google/protobuf/src/Google/Protobuf/Internal/GPBUtil.php on line 182

@PierrickVoulet
Copy link
Collaborator

I think you are experiencing the same issue as #105.

You previously said that you use the latest version of the library which is great but I see from the logs that you still use the V1 namespace though.

I advice you to update your code to use the V2 namespace instead as it comes with several improvements and bug fixes including one that should fix the issue you are describing here.

@fiboknacky
Copy link
Member

Closing because an answer is provided.

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

No branches or pull requests

3 participants