Firebase show success notification but this chrome extension domain did't show in list of authorized domains. I tested in other project in other account but getting same problem. let's see the photos
Firebase has fixed this bug after 4 days
Related
Well, it's quite simple actually... I'm trying to use nodemailer but everytime a try to call the mailer fucntion, it returns an auth error. I searched the error and apparently it's cause because of Google "less secure apps access" (https://myaccount.google.com/lesssecureapps) option, it has to be enabled, but the problem is: since may 30th of 2022, Google updated it's policy, and no longer has this option, so i can't use nodemailer in gmail anymore?
enter image description here
enter image description here
I tried to search the problem and find how to enable the "access to less secure apps" on Google gmail account configuration, but since Google updated it's policy, and they removed that option, i can't find any other solution. I didn't find anyone else with this problem either.
if you enabled 2fa on your google account you can create an apps password.
you can then use the apps password in place of your actual Gmail password in your Code
how to create an apps password
I am creating Google Smart Home action of google home. But I have not idea, how to connect the dynamo DB with smart home action but I can see here using with firebase. When I ran the command with invocation name in google assistant then it is showing "something went wrong".
I have enabled the home graph API and also created the JSON key file. I also can see their upload JS file button but don't know, what files should I upload there?
Thank You
It sounds like you are going through the Washer codelab, which is a great first step.
When you are configuring your project in the Actions console, you would need to enter your fulfillment URL from your application (rather than the Firebase URLs shown in the codelab).
You also need to set up an authentication server to enable account linking. Once you've completed this, you should be able to test your Smart Home Action through the Google Home app. Remember that you need to configure the console with your application's URLs for authorization and tokens in place of the demo URLs in the codelab.
The JS upload you are seeing in the console is for local fulfillment applications, which would be a feature to consider adding after you have successfully uploaded and tested your Smart Home Action.
We customised our Azure AD B2C tenant's Combined Sign-Up/Sign-In Policy to serve up our own login page. This worked across all the major browsers when we tested last week, but it stopped working today for some of our users on Chrome and Firefox.
We are getting this 404 error when some of our users browse to our home page and they get redirected to the login page (our B2C tenant and custom login URL is redacted but all other query parameters are unchanged):
https://login.microsoftonline.com/redacted.onmicrosoft.com/B2C_1_sign_up_in/api/CombinedSigninAndSignup/error?code=UX004&diags=%7B%22version%22%3A%222.0.0%22%2C%22user-agent%22%3A%22Mozilla%2F5.0%20(Windows%20NT%2010.0%3B%20Win64%3B%20x64%3B%20rv%3A54.0)%20Gecko%2F20100101%20Firefox%2F54.0%22%2C%22online%22%3Atrue%2C%22trace%22%3A%5B%22%231%20T005%20(3ms)%22%2C%22%232%20T027%22%2C%22%233%20T021%20(37ms)%22%5D%2C%22code%22%3A%22UX004%22%7D&csrf_token=YzQ0N3F3NXlTVzBVWTFraG96cmlVU3FVbjVNRmZRbHZ6RURIaHdPRExNRTlDRVRNL3hPN00xRXhoOUV0bnE0V3pYc3ZYcEg0YzRhVnp5WE5QYTJZN0E9PTsyMDE3LTA4LTA4VDAwOjU3OjM2Ljc3MjM1MDlaO283Mm9nSFVXb3lIbWtVZy9CeHZVbFE9PTt7Ik9yY2hlc3RyYXRpb25TdGVwIjoxfQ==&tx=eyJUSUQiOiI4MDgwNWE3Ny02OTU2LTRiNGMtYmUyYi05OGZkZGEwYzM4MDkifQ&desc=https%3A%2F%2Fourdomain.redacted.html
We have tested the following with no success:
Clearing all our cache and cooking
Disabled all extensions
Private browsing/Incognito mode
Chrome on Android
But Internet Explorer loads the custom sign-in page just fine on their computer!
I have tried searching online for error code UX004 but didn't find anything. Can someone from Microsoft advise what this error code means? Thank you.
I didn't get any response from Microsoft, but we tried various fixes. The one that worked for us is to apply a SSL certificate issued by a commonly-trusted issuer on our test domain. I can't confirm that this error message means AAD B2C is complaining of an insecure connection, but it's worth exploring in case it works for anyone else too.
It appears as though this may be a CORS issue on your hosted login page. Use (F12) to open up your developer tools, look into the Console tab and ensure you have Preserve log switched on. Navigate to the website and hopefully the error should be visible.
For me it was a CORS issue with the storage account. Adding a CORS rule that allowed everything solved the problem.
Go to azure portal (https://portal.azure.com) and open the storage account that contains your custom login page templates. In the right hand navigation find Settings > Resource sharing (CORS)
Add a new rule with the following values
Allowed origins = *
Allowed methods = Select all items
Allowed headers = *
Exposed headers = *
Max age = 200
Hopefully that helps!
I'm trying to follow the AdSense API getting started guide, and I'm getting stuck on the 'Register your application' section.
I have created a project, but I can't find the 'Activate' button. Instead I go to the API Manager, and then the Library tab, where there is a ton of API's listed.
When I click 'AdSense Management API', the site eventually reports 'The API "adsense" doesn't exist or you don't have permission to access it', after about a minute of processing.
I tried adding in the analytics API, and it worked just fine.
Is there a step I'm missing? Do I need to submit an application to Google somewhere?
Thanks for your advice.
This was a silly mistake. The browser I was using ad adblock installed. Disabled adblocking for this site, and everything is fine.
We are using the Rest V2 API to create an envelope with a document in it. We then redirect the user to the page for them to complete the document (drag tag etc). using the demo server and our developer login we get a message saying the user has been logged out due to inactivity. On the production site with a production account it works OK. We can log into the demo site without issue with our account.
There was a bug in the new version (which goes on demo.docusign.net first), that bug should be addressed by now. The great news is that no production servers were affected and by the time the new version will make it to production the bug will be fixed. I believe demo servers will get the fix tomorrow.
Thanks for choosing DocuSign API!