I created a SmartHome project with all information provided (all checks are OK in project overview).
When I go to Deploy > Release and click on Submit Production then Submit for review an error occured:
Conversation fulfillment ... has invalid API version '0'
Any idea whats's wrong ?
Problem fixed by Google internal team (direct contact to support).
From aog-support#google.com:
I received a response from our internal team that the issue has been fixed. Please re-submit your Action for review and let us know if the issue still occurs.
Related
I am in need of assistance with my Meta's Conversion API and Google Tag Manager setup. I have successfully set up a web and server container, with the server container being manually configured and running on AWS.
I am currently working on the "Publish resources" section, but am encountering an error that says "Publishing failed. We were unable to publish the resources to your Google Tag Manager account. Please try again." I would greatly appreciate it if someone could provide some guidance in resolving this issue.
For reference, my web container is running on web.example.com, the tagging server is running on tagging.example.com, and the preview server is running on debug.tagging.example.com. I have followed this guide to set up my server-side tag manager on AWS: deploy-server-side-google-tag-manager-aws/.
Here are some screenshots:
The error
Console error
Console error link
I google-searched for this error and all I can find is other people with the same error but no solution was provided. I have also emailed Google and Meta support but I haven't gotten a response yet.
While i'm trying to push my selenium code to bitbucket using "EGit - Git integration for Eclipse 5.4.0", getting the below authorization error,
Error Detail:
https://name#bitbucket.org/name/testing.git: not authorized
https://name#bitbucket.org/name/testing.git: not authorized
I have my company account and my account is registered with company email which is managed by Google , eventhough I have provided correct credentials I'm getting this authorization error . I have tried giving many different combinations but getting into the same error.
Can anyone please tell me what is wrong with it, Is there any settings i have missed out or any other things i need to do to overcome this error and push the code to Bitbucket.
Attached the image of the error for reference, if anyone can guide me on this,will be much grateful.
Thanks in advance!!
I've recently integrated play-silhouette 4.0.0 with Play 2.5 to handle authentication. I am allowing my users to login with Google and as such am using Silhouette's OAuth2 features. I am redirected to Google's authorization page properly but after pressing allow the app fails with
403 - Project marked for deletion
I have enabled the Google+ API in the developer's console and am requesting the scopes "profile email" from the service. I've also deployed the sample app and get the same error. The error codes listed by Google are not much help - anyone have an idea? I've been testing on my local machine.
I resolved this issue:
Create a new project in the Google Developer Console.
Enable Google+ API.
Create OAuth Credentials.
Perhaps I created the credentials before I enabled the API. Seems a bit silly order would matter. Hope this is helpful to someone else!
Up until today, I have been successfully developing with PayPal's sandbox using the new PayPal PHP SDK which comes preconfigured to use this sandbox URL:
https://api.sandbox.paypal.com/2.0/
(URL in Chrome currently returns: "Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.")
But today my webapp is crashing due to a SSL handshake failure:
Uncaught exception 'PPConnectionException' with message 'error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure' in ./paypal-sdk-1.0.92/lib/PPHttpConnection.php:185
The only event that has occurred since yesterday (when my webapp was last working) was I reset my sandbox "seller" account, which may have reset the API credentials according to this post. Since I've updated the API credentials manually, and have verified them to be correct, I cannot say if they were ever wrong at this point.
After lots of searching, I found other web articles that say the URL should be:
https://api-3t.sandbox.paypal.com/2.0/
(URL in Chrome returns a SOAP response.)
So I changed my PayPal PHP SDK's included URL from https://api.sandbox.paypal.com/2.0/ to https://api-3t.sandbox.paypal.com/2.0/ and it is working perfectly again. What happened here? Is the non-"3t" sandbox URL simply broken right now?
EDIT: After the feedback received from #Win and #JoelP, I have filed a bug report through the PayPal SDK github so someone at PayPal can explain what changed today and fix the SDK to have the correct URL when using Signature credentials.
EDIT 2: PayPal fixed the issue a few days ago. It's going to be available in the next release. https://github.com/paypal/SDKs/issues/22#issuecomment-8660682
Thanks for the help everyone.
Differences are between Certificate and Signature
Signature is the preferred way of accessing PayPal API.
The issue is fixed and the code has been pushed to master branch. You should see the refreshed bundles of the sdk out on x.com in the next couple of days.
Refer GitHub issue here https://github.com/paypalx/SDKs/issues/22
Thanks,
Prasanna.
I can't answer the question but I can say that I have just discovered the same problem. I confirm that jimp's workaround of changing the SDK's service endpoint config to :
service.EndPoint="https://api-3t.sandbox.paypal.com/2.0/"
solved my issue. (This is in the Paypal SDK config/sdk_config.ini file).
In my case I am using the PHP SDK. I have not changed anything on my sandbox account. My best guess is that the original URL is simply down for a while. (Firefox shows the "Secure Connection Failed" alert).
When I go Add Google API's and click on any API I want to download I
get the following error
"There was a problem downloading the API bundles, See Error log for
more details" Can any one help me figure out what might be going wrong
and where is this logs location ?
The Error Log can be accessed by clicking on Window - Error Log.
The server is currently malfunctioning and returning HTTP Error 502 (Bad Gateway). It should be a transient issue, though, and everything should be back to normal soon.