Can't register new Client ID on Instagram developers page - instagram

I can't register new client because always have a wrong captcha, I tried to create it with different browsers but same effect :(
The captcha solution was not correct. Please try again.

I used the Content-Security-Policy extension for chrome.
https://github.com/PhilGrayson/chrome-csp-disable
Then the field appeared -> New App Created.

The form is broken.
I've been trying it on and off for the last two weeks, also with different browsers, it doesn't work.

I have exactly the same problem when trying to create an client ID. I've send in a ticket for a solution.

you can see my answer there you have to install google chrome extension and then don't forgot to disable the Content-security policy
https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden
you see here too
https://stackoverflow.com/a/53188447/5889990

Related

Gmail - Link to Draft in non-conversation view

I am importing/creating drafts in Gmail using the Gmail API. After creation I'd like to redirect the user to the Gmail UI with the opened Draft in the composer window.
I made it work properly for https://mail.google.com/mail/#drafts?compose=[MESSAGE ID]. Other urls I found here also worked well. Gmail is doing some redirects and eventually the composer window is opened with the draft.
Now my issue:
If the user has not enabled "Conversation view" this will not work at all. The redirect will then result in https://mail.google.com/mail/u/0/#drafts?compose=new and only an empty, new composer window is shown and a new draft is created by the UI.
If I open the draft directly the ID-format is different. https://mail.google.com/mail/u/0/#drafts?compose=hJzgZpSqgLQcCWgZqnlNRzRBfMbjZVnZklzvcFxhQCdwT... and I have no idea if this format can be generated somehow.
Does anybody has an idea or experience to also make it work with this UI setting. How I can force Gmail to load the draft into the composer window?
Thanks in advance.
If you have Email Threading > Conversation View enabled
Make use of the following URL
https://mail.google.com/mail/u/0/#inbox?compose=DRAFT_MESSAGE_ID
If you have disabled the Email Threading > Conversation View option
Make use of the following URL
https://mail.google.com/mail/u/0/#inbox/DRAFT_MESSAGE_ID
Additional information
The main difference between them is that the first is treated as a conversation while the second example is not.
You can use #drafts instead of #inbox in the URL.
The number after .../mail/u/ is the session you have opened
You can retrieve the DRAFT_MESSAGE_ID by making a request to the API
You can approximately generate the compose ID by yourself, there are some examples out there (not recommended). I strongly recommend you to use the DRAFT_MESSAGE_ID instead.
This appears to still be an issue the one solution I did find was that you can find your draft directly (even though it would be the last draft) and go through multiple accounts by redirecting to
https://accounts.google.com/AccountChooser?authuser={user account}&Email={email account}&continue=https://mail.google.com/mail/#search/rfc822msgid:CAMU-31NcJCVHyGNsAycRKfuS0nMonoaZ6wFMD90Sej996qjuPQ#mail.gmail.com
You need to get your message id toi replace the area from <> from your draft. So you'll have to create the draft first. Get the google message ID, then use that with messages/get to get the Global Message Id (also referred to as message id) and then use that with a search. At this point you'll open a page with a search to a single draft but it will not be opened. Your users will have to click on the one message. Unfortunately there does not seem to be a way to have the good way work for conversation view, and this way work for non.
I tried many different URLS and nothing worked. As noted in the original question, it might work that you could link to the full URL but I see no way to get that. If you spend long enough working with an email you'll even find that ID changes so they aren't even stable within a single day.
Another solution that could work is as explained:
https://mail.google.com/mail/u/0/#inbox/DRAFT_MESSAGE_ID
But as noted this does not open the draft on the first time you go there. It seems you have to travel to that link 2 times in a row to get the message to appear. I guess you could go to the page maybe inject some javascript to go to the page again but I don't know how to do that.

How can I sign in to Google inside a Chrome Extension browser_action?

I’m trying to keep this as simple as possible so that it can be a resource for other people in the same situation.
How can I sign in inside of a chrome extension, which is not a hosted web server?
I seem to get an error “Invalid Cookie Policy” whether I use both the button approach or gapi.load(‘auth2’) followed by gapi.auth2.init(), regardless of including client_id in <meta>, manifest.json, and init
If anyone can get it working (sign in and id_token, not the auth token), please leave an answer!
Thank you
I have followed this tutorial from official Chrome Documentation and had no problem

sign up google merchant account

I need some advice on setting up merchant account in google.
When I try to set up merchant account, account signing up page shows me an error.
The error code is shown as "An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}"
I've tried to resolve this issue with Google support team, but they keep sending me general information and manual..
Please give me suggestions on this issue. (I already finished developing my commercial application, but can't set the price because of this issue. )
Thanks in advance.
I had the same issue.
What I did to resolve it was to flush the browser cookies, history and cache. After that, I opened a new browser tab and logged in to my Google Wallet account (the one I set up previously to BUY apps on the play store). As I was logging in, I noticed there was some error but it quickly resolved itself - I successfully logged in and could see what I previously bought.
After that, I closed and re-opened my Google Dev Console, and tried to setup a Merchant Account again and it worked.
I experienced the same problem and I finish solved changing my address length, uou can't use more than 64 characters. see https://stackoverflow.com/a/21412790/2359141
clear cache and everything by using ctl+alt+delete
keep only one tab
Select proper product type , I selected Computer software its worked for me
Do sign out and login in wallet google
I found the solution.
You just have to let the VAT number empty during registration, fill it later.
It worked for me.
I got the payload error as well, what resolved my problem was changing my PO Box address to a physical address. Google chat support figured it out.

Google Ical import for our Azure web app fails

We have developed a SaaS solution on Windows Azure. We generate Ical feeds for the appointments in our applications for every user.
The Ical seems to work on outlook, iphone etc.
Google calendar is the only one where it does not work.
We work with a SSL certicate signed by GoDaddy.
When working with a normal http connection the Ical seems to work like normal.
I would assume google accepts the certificates from GoDaddy but there still seems to be a problem?
I had different situations:
Our events pop up but then disappear again and we get the error: 'Could not fetch the URL'
Or our events pop up but we keep getting the message 'Importing calendar for URL'. That message stays there forever. When refreshing our events will stay but will not be updated.
Validating the Ical with http://severinghaus.org/projects/icv/ works.
Downloading the .ics and inserting it manually works as well.
Any help?
Kevin,
Google is having an issue right now with all iCal feeds, which is most likely the cause of your problem. The symptons are just as you described, they show up and then disappear.
Google hasn't come out and admitted anything yet, but it's obviously something on there end. Hopefully we get a fix soon, I'm in the same boat as you.
You can follow the issue here:
http://productforums.google.com/forum/#!topic/calendar/tB7ICbqeLpo
Problem seems to be related to your SSL certificate. Similar question was answered here Google calendar can't import my ical file

How to logout of an HTTP authentication (htaccess) that works in Google Chrome?

I got a solution for Firefox and IE but I didn't find any solution for Google Chrome.
Is there a way to do it in Google Chrome?
I know it's a really old post... I mean like friggin 5 years now, but I just found a somewhat good solution.
Inside your protected folder, create another folder, let's call it "logout". Place the same .htaccess file in here as you have in your protected folder, except with a small modification.
instead of:
Require valid-user
now write:
Require user EXIT
And make sure, you don't have a user named exit! :D
In your protected area, your logout link or button or whatever, should redirect the user to this address: example.com/protectedFolder/logout
The browsers usually are able to keep only one user logged in from one site name or realm name... the sign in attempt for the user Exit will overwrite everything, thus the originally logged in user, would have to log in again to the protected area.
But as always, I might be wrong, and you should still close all your browser window, and restart the computer if you want to be sure! :)
Also, it wouldn't hurt, if you would tell your users what is going to happen, when they hit logout!
I have tested this in chrome and in internet explorer 11.(will not work in edge, and maybe others neither)
The solution was found here:
https://www.mavensecurity.com/media/BasicAuthLogOut.pdf
You can't logout a HTTP authenticated session other then closing the browser window. Also see the accepted answer on this question for an extensive explanation.
try redirect to:
wrong_user:wrong_password#yourdomain.com
I have put together the following article which explains how I have managed to achieve this in Chrome. I hope this helps. https://www.hattonwebsolutions.co.uk/articles/how_to_logout_of_http_sessions
In short - you create a sub folder (as per Gyula's answer) but then send an ajax request to the page (which fails) and then trigger a timeout redirect to the logged out page. This avoids having a secondary popup in the logout folder requesting another username (which would confuse users). My article uses Jquery but it should be possible to avoid this.

Resources