I am trying to run quickblox sample chat application which I got from following link
https://github.com/QuickBlox/quickblox-dotnet-sdk
Issue here is, when I run the app, it fails to load base session and gives error such as "{"errors":["Token is required"]}". I tried to debug it but could not find the root cause of it.
(Example code is using Quickblox sdk 1.2.2, which I tried to upgrade to 1.2.7 as well but in that case also still that issue remains)
The method inside sdk uses service call to api (http://api.quickblox.com/session.json) for getting session, which I tried to call by using Postman (google chrome extension), in which case I was able to get the session in response. Strange it is.
Does anybody know what is wrong with the example?
Update: I tried to manually write http call for getting session. Now in this case, I am no more able to access dialogs and other api calls are also failing(getting forbidden error in almost all sdk api calls after authenticating).
Could anybody tell me what is going wrong here?
After spending complete day found the fix. It was really small issue. Currently sample in github is using http://api.quickblox.comas a api end point, change it to https://api.quickblox.comand it will start working. Note the 's' in url.
The best way to do this is by using the account settings API.
Related
when i try to add new file in WSO2 to make new api and im done making the flow and try to run it.this the image that runtime not showing the url i can run it but the link for testing the api in the postman not appear, somehow that made it too hard for me to get the link
i try to find it in google but none in their can solve my problem, i think if the runtime service run normally, that can make us more easier to get the link for testing in postman
I not hugely experienced with API's, but I was wondering the difference in Postman with using the 'Authorize using Browser' below Callback URL and not using it. (I'm trying to connect to Microsoft Dataverse using Web API) When I don't use it a pop up comes up fine and I can sign in and authentication goes great. But if I use the browser it won't work. Now, I don't have Azure Admin rights to set up callback URL's in my environment so I imagine that is part of the issue, I'm just wondering why it works one way and not the other. I was trying to replicate in python and am getting the same error as trying to use browser in postman. I would like to understand what backend process Postman is using in the non-browser version so I can replicate if possible. I followed Microsoft's example in the link below as well.
Postman Example
https://learn.microsoft.com/en-us/learn/modules/common-data-service-web-api/3-postman?ns-enrollment-type=learningpath&ns-enrollment-id=learn-dynamics.integrate-power-platform
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
I am trying yodlee api on android but getting file not found exception when I called HTTP GET request on : Request URL=https://developer.api.yodlee.com/ysl/restserver/v1/providers?name=icici.
When I used java sample api as standalone java application it's work fine but in android it is giving exception. cobrand as well member login works fine on android.
You should first check the code, as this is not something which Yodlee API returns. Seems to be an issue with your android code. Do you mind updating the question with your code and actual exception you are getting?
I am having trouble with facebook API call. I am using Koala for server side api call but recently came into issue making api call. So I tried to bypass koala call and did raw api http call using call but to no avail.
When I do curl from development machine it works fine.
curl "https://graph.facebook.com/me?oauth_token=my_token
It returns profile details, but the same thing done from production machine, it's throwing the exception
{"error":{"message":"Cannot call API on behalf of this user","type":"OAuthException","code":200}}
Does anyone had the same issue? Like to hear from you guys.
I found the source of the problem (on our site, at least). In Facebook's developer console (https://developers.facebook.com/apps), our app was showing an invalid privacy policy. Due to this, Facebook had automatically placed our app into Sandbox Mode.
Updating our privacy policy and (more notably) removing our app from Sandbox Mode caused this error to cease.
Other users seem to have had some success with removing regional (country-specific) restrictions on who can and cannot log in to their app (https://groups.google.com/forum/#!topic/django-social-auth/XaE5dFXEqhA)
Best of luck! :)
I had the App in dev mode. All I did was remove the subscription & resubscribe my webhook server and this worked for me.