When trying to log in with an account in my website, I'm always getting 0.1 score in reCaptcha response in mobile.
When I try to log in in desktop, I get between 0.7 and 0.9 all the time, but when I switch to the mobile emulator in Chrome Dev Tools, I'm always getting 0.1. I also tried with my smartphone and the same issue happens.
I tried the code in my local machine and in a dev server and I'm always getting the same error.
The response object I get from the reCaptcha API is the following in mobile.
{
"success": "1",
"challenge_ts": "2019-10-07T09:46:46Z",
"hostname": "<either localhost or my dev server address>",
"score": "0.1",
"action": "login"
}
If I perform the same action in desktop mode, the score is between 0.7 and 0.9.
I guess I'm doing everything right, as I'm getting the reCaptcha response properly but when I try in mobile mode I always get the 0.1 score.
Related
I trying to use new mode recording from Agora Here.
But It doesn't work for me. I always got Error 404 with message ('no Route matched with those values')
Here is my url path
'/v1/apps/{appid}/cloud_recording/resourceid/{my-resource-id}/mode/web/start'
I already check on Cloud Recording RESTful API to find pattern for request body but It doesn't said anything about Web Page Recording. (Maybe because It's just beta for now)
Here is my start request body that I copy from tutorial but It doesn't matched with RESTful API
const extensionServiceConfig = {
errorHandlePolicy: "error_abort",
extensionServices: [{
serviceName: "web_recorder_service",
errorHandlePolicy: "error_abort",
serviceParam: {
url: "myurl",
audioProfile: 0,
videoWidth: 1280,
videoHeight: 720,
maxRecordingHour: 2
}
}]
};
The "404 No Routes" error is caused by Cloud Recording not being enabled on your project. To enable cloud recording on your project, you’ll need to click into the Products & Usage section of the Agora.io Dashboard and select the project name from the drop-down in the upper left-hand corner, click the Duration link below Cloud Recording.
Here is a step by step guide I wrote: https://medium.com/agora-io/agora-cloud-recording-quickstart-guide-with-postman-demo-c4a6b824e708
Also Agora offers a Postman Collection that provides a sample body for making a request and if viewed through the Postman app it will generate the JavaScript snippet for you.
I am currently writing an app in ASP.Net Core 3.1. Everything has been working fine on localhost (IIS Express) for weeks, but all of a sudden, my authentication has stopped working.
I am using AzureADB2C for authentication. Whenever my app needs to redirect to the login page, I get the following error in Edge/Chrome.
Hmmm… can't reach this page
It looks like the webpage at https://localhost:44344/ might be having issues, or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR
The browser also displays a warning telling me that the Connection to this site isn't secure
When I use the Azure Portal to test my user flow, I can see that Azure is redirecting me back to https://localhost:44344/AzureADB2C/Account/Error#id_token=eyJ0{snip}. The token actually seems to be valid, but I am not sure why Azure is redirecting to an error page.
Here are my Azure Ad B2C settings
"AzureAdB2C": {
"Instance": "https://MY_COMPANY_NAME.b2clogin.com",
"ClientId": "MY_CLIENT_ID",
"CallbackPath": "/signin-oidc",
"Domain": "MY_COMPANY_NAME.onmicrosoft.com",
"SignUpSignInPolicyId": "B2C_1_SignUpSignIn",
"ResetPasswordPolicyId": "B2C_1_PasswordReset",
"EditProfilePolicyId": ""
},
Everything was working perfectly fine this morning. After restarting my PC, I launched Visual Studio, and my app would no longer work. I tested my app on another PC, and got the same errors.
UPDATE: After testing my user flow in the Azure Portal, with my local app not running, it looks like Azure is correctly redirecting back to https://localhost:44344/signin-oidc#id_token={token}. So the redirect to the error page is happening within the auth middleware. No errors are written to the output window, so I have no idea what is going wrong.
I tried rolling back my app to a previous commit from a week ago, but I am still seeing the same issue with older code that used to work.
This appears to be an issue with Windows. I recently updated to Insider Build 19587.rs_prerelease.200313-1639 and that's when the issue started occurring. After rolling back to 19582.rs_prerelease.200306-1640, my app authentication started to work again.
I recently started using the foursquare API, but suddenly I get "Consumer disabled" error responses.
So far, the only API call I've been doing is one to browse some venues:
https://api.foursquare.com/v2/venues/search?ll=51.222816,3.224778&query=Friet&radius=200&limit=10&categoryId=4d4b7105d754a06374d81259&client_id=app_id&client_secret=app_secret&v=20161116
These are the parameters I am sending:
ll:51.222816,3.224778
query:Friet
radius:200
limit:10
categoryId:4d4b7105d754a06374d81259
client_id:app_id
client_secret:app_secret
v:20161116
At first everything went well, then I started working on some other part and now I'm back to foursquare and getting the following response (with 403 http status code):
{
"meta": {
"code": 403,
"errorType": "not_authorized",
"errorDetail": "Consumer disabled."
},
"response": {}
}
I've searched my emails, but I didn't recieve any warnings or notifications on why this might be happening. Anyone had any experience with this?
One thing that may be of importance: Since I'm in development and there is no site for the project yet I can not provide a privacy policy url in the app settings. Because there is none, yet.
Edit: this is my client ID: 1VXNUT53J2OMMTMKA4E3UBKYLQQCI1GC3CRCCBPSQK1BWQFG
try resetting your API secret at (https://foursquare.com/developers/app/CLIENT_ID/reset)
That error could happen if there's suspicious behavior on an API key - but you would've gotten an email first.
Update: I see this key flagged as disabled. I re-enabled so should be working now. I'll run through the logs and try to figure out how/why this happened.
So the problem I'm facing is uploading large video files trough Youtube API v3.0.
I'm folowing the steps specified here.
So I thought that the issue lies in access token, becouse it's valid only for 3600 seconds. So I got the refresh token from OAuth Playground. And I get the fresh token when user starts the upload on my Youtube channel. After 50 minutes i abort the PUT request, get the fresh token and resume upload like specified in documentation. The problem is that after one hour I get response:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType": "header",
"location": "Authorization"
}
],
"code": 401,
"message": "Invalid Credentials"
}
}
Everything works fine when upload lasts less than one hour. But when uploading big files on slow broadband the upload fails. What am I doing wrong?
I'm making the requests in JavaScript with jQuery. I double checked the steps in documentation, and if it works with smaller video i think the script is ok.
Even this script fails to upload after one hour, the progress bar comes to 100% but then it gets 401 response.
Thank you for your time, and sorry for my bad english.
I am developing a Vine client for Windows Phone 8 but I'm having trouble accessing their API's from desktop or mobile Internet Explorer.
When, for example, I go to "https://api.vineapp.com/timelines/graph" in Google Chrome I get a response:
"{"code": 100, "data": "", "success": false, "error": "You must be logged in to perform this action."}"
but when I do the same from the desktop Internet Explorer I get "400: bad request".
I get the same error on IE on WP8 and my Lumia 920.
Anyone know the cause and a possible solution?
Imo, that's actually a "bug" or rather unexpected behaviour in non-IE browsers. The error code is the same as the server replies with a 400 BAD REQUEST error.
If you access this via any real API, the response will be the same from all browsers; it's only an understandable decision by Microsofts to not show strange error messages (Content-Type: application/json) to end users.