I am trying to integrate with Line using Smooch. Everything is fine except I am not able to receive the message from Smooch to Line APP.
Giving Forbidden Error.
Below are the logs from Smooch Dashboard.
Line to Smooch----OK
Smooch to HTTP ---OK
HTTP(API) to Smooch --OK
Smooch to Line -- Error: Forbidden
403 Forbidden - Your credentials are valid but you don’t have access to the requested resource.
I am not sure which resource is not accessible.
Any help is highly appreciated.
Thank you
The membership plan was not allowed for PUSH Messages.Now it is working after membership upgrade on LINE.
Related
I´m using dialogflow with http request on a project that works in twilio, with the recent need of migration to v2 API of dialogflow the client access token will not work. Reading the new authentication, I generated the json following the instructions in the google cloud docs, but can´t make it works. Because I need to do all the interaction through POST requests to the dialogflow agent, does anyone know how I can generate the authentication token well?
{
"error": {
"code": 401,
"message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
"status": "UNAUTHENTICATED"
}
}
Thanks
This is the function code that today works to make the http request. The problem is that all the services are in Twilio and i dont have access to the server, for that I cant define the environment variable.
Twilio Function code
Twilio Fuctions uses NodeJs and allow me to install many npm modules, with the following limitation: "Native Packages Not Supported - Functions does not provide a C/C++ compliler required to complie native addon modules. This means modules that depend on node-gyp can not be installed to Functions."
I don´t know if this limitations affect service acount working to me in this case.
J added all the roles.I still cannot get terraform to build the project.
googlecompute: Error creating instance: googleapi: Error 403: Required 'compute.zones.get' permission for 'pr
ojects/terraform-3/zones/us-central1', forbidden Build 'googlecompute'
errored: Error creating instance: googleapi: Error 403: Required
'compute.zones.get' permis sion for
'projects/terraform-3/zones/us-central1', forbidden
This sort of issue might arise if somehow your cloudservices robot gets removed as a project editor. My best guess is that in your case this is the issue.
This might happen due to API call which has SetIamPolicy that is missing cloudservices robot from the "roles/editor" bindings. SetIamPolicy is a straight PUT, it will override with whatever policy is provided in the request. You can get the list of IAM policies for your project with below command as given in this article.
gcloud projects get-iam-policy [project-id]
From the list, you can check whether below service account has the editor permission or not.
To fix the issue, you can grant the mentioned service account "Editor" permission and check whether that solves the issue or not.
[id]#cloudservices.gserviceaccount.com
I am trying to enable push notifications on my website using VAPID keys.
When i include the gcm_sender_id and remove the applicationServerKey from the pushManager.subscribe method, it runs fine.
Only when i enable VAPID keys and remove the gcm_sender_id from manifest.json file. i get the foloowing error.
DOMException: Registration failed - push service error
I am using Chrome browser.
I encountered this error in Brave browser. By default, Google Services for push messaging are disabled in Brave. To enable this, open the following URL in brave:
brave://settings/privacy
After this, enable the flag "Use Google services for push messaging":
Source:
https://github.com/firebase/firebase-js-sdk/issues/3195#issuecomment-848036637
The applicationServerKey that i was using in the pushManager.subscribe method was somehow incorrect.
It worked when i regenerated the keys in node using the following module.
const webpush = require('web-push');
const vapidKeys = webpush.generateVAPIDKeys()
In my case,I was trying to run firebase messaging on a flutter web.
My Browser was BRAVE.
It always failed with an exception of firebase fcm registration push servic error.
I followed #Nicodemuz answer, but it didn't solve the issue. I get the same error.
The only solution was setting Google chrome as my executable.
Anyhow the issue is not with firebase or flutter, it's with the brave browser itself.
I am implementing yii2 authclient, I created the client id in in google api console this is the redirect url I created in gogle console with the corresponding client id.
http://mysite.x10host.com/oauth2callback
when I access my site login this is how it looks like
http://mysite.x10host.com/home/mysitex/public_html/web/site/login
when I click the the google icon
That’s an error.
Error: redirect_uri_mismatch
Application: Project Default Service Account
You can email the developer of this application at: myemail#gmail.com
The redirect URI in the request: http://mysite.x10host/home/mysitex/public_html/web/site/auth?authclient=google
can someone help me on this.
Thank you in advance
I use foursquare API in an application. I have no issues when I run the app on my local machine but on a server I get this error after the user allows the app and is redirected to the callback url.
Fatal error: Uncaught exception 'EpiFoursquareException'
in /home/content/40/9029540/html/earlybirds/test/lib/EpiFoursquare.php:252
Stack trace:
#0 /home/content/40/9029540/html/earlybirds/test/lib/EpiFoursquare.php(208): EpiFoursquareException::raise(Object(EpiCurlManager), false)
#1 /home/content/40/9029540/html/earlybirds/test/lib/EpiFoursquare.php(196): EpiFoursquareJson->__get('response')
#2 /home/content/40/9029540/html/earlybirds/test/callback.php(45): EpiFoursquareJson->offsetGet('access_token')
#3 {main} thrown in /home/content/40/9029540/html/earlybirds/test/lib/EpiFoursquare.php on line 252
Anyone knows the reason?
I use PHP and mysql
Make sure you send the redirect_uri param when building your auth url and that it matches the one on the APP details page. I had to make two apps, one for testing locally and one for testing on my dev server which had, of course, a different URL.