Just read on Google's Group for Wallet merchant support that the forum was being moved here, to stack overflow. Anyway, this is really a question for google's engineers. I have updated the postback URL multiple times from our google wallet merchant account, and every time have been greeted with the following message: "An unexpected error has occurred. Please try again later."
Later, when I refresh the page a few minutes following, the new postback url that I entered will appear to have taken. However, our merchant account will still not postback to the right URL. Sometimes this corrects itself 6-8 hours after entry --- other times it does not.
What gives? I'm very frustrated with google's in-app digital goods service for the preceding reason and am close to seeking out an alternate solution (even after 10+ developer hours implementing this with our subscriptions registration system)
Related
The problem is that in Manage Clients at https://www.instagram.com/developer/clients/manage/ client was created,
but it became invalid, the id did not work, i.e. instagram disabled it, the inscription was disabled.
We decided to delete the old client and create a new One, but instagram does not register it. The line of consent and the captcha does not issue. Respectively writes 2 errors:
1.Incorrect Captcha. Try again.
2.Error sending: fill in all required fields.
How can this be corrected?
I've had this same issue, and haven't been able to get anywhere with it. The support page for Instagram says to report a bug using the "Report Bug" button on the Developer Dashboard (http://instagram.com/developer/clients/manage/). If you click that button it takes you to a form that asks if you want to report a bug for the old API or new API. If you select the old API it says "we're not taking bug reports for the old API", if you select new API it takes you to Facebook's developer support page. I created a ticket there, and they told me I had to report it through Instagram's support links. WTF?? That's what I did .....
Anyways, the problem is related to a bunch of javascript errors on that client registration page. I first encountered this problem about 3-4 weeks ago, and it's still around. Feels like IG really doesn't give a crap about their developer community ....
Everything that I read about AdSense says that I need a website (blog, domain, etc.) which I do plan to get. I'm just not sure about the name of the domain that I want.
However, I want to be moving on, because the address verification letter from Google may take several weeks.
So, I would like to put in the domain that I think that I'm going to use. Can I do that, even though I don't own it (yet)?
Do they check if it's registered? Or are they just saying that it won't work because I can't access the HTML (yet)?
Do not register yet if your website is not ready.
Google will manually check your site whether it is eligible for Google AdSense. If they don't see any or poor content, they will decline your site and you will have to wait several weeks, maybe even months to re-apply for the same site. What you should do is finalizing your website until it's 100% ready, put content on it, and – most importantly – drive some visitors to it. At the very beginning you won't earn much anyway when you only have a little amount of visitors. When your website gets more popular, you should apply for your site and in most times your website gets approved in a few days.
You then have to wait for the letter, that's right – but you can already create ad tags, show them on your site and earn money like any other AdSense user. The letter is sent for verification and you can't request a payout before you didn't verified your address and bank account, but you will have to wait for $100 anyway (or the equivalent in your currency) since that is the minimum payout. After you achieved $100 at the end of a month, you will have to wait an additional 21-23 days to see your payment in your bank account.
So finish your website, put content on it, register for AdSense. You can wait for the letter while you already see earnings in your account.
I was using the following api to get the latest 3 posts from public accounts to show on the website:
https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3
I had created an app to get the client-id.
However from today, this API has started throwing the following exception:
{
meta: {
error_type: "OAuthAccessTokenException",
code: 400,
error_message: "The access_token provided is invalid."
}
}
Could you please let me know as how to resolve this?
Based on the date, you probably have an older app that got hit by the API migration today, like mine. In short, Instagram decided to make developing for their platform WAY more annoying by requiring all API requests to be authenticated per user, even for data that users shares publicly. So you (like me) will likely be redesigning you app entirely.
To tell, log in to instagram.com/developer and click manage clients; then hit edit next to the set of keys your're trying to use. Up near the top, it will have a section called 'Client Status' -- if yours reads 'Sandbox Mode', fun times ahead! Hopefully you interact with less than 10 users and can stay in sandbox mode, otherwise you'll have to write an essay, film a video, and basically plead to get your permissions back (probably in a few months, when some Instagram intern finally digs his way down to you in the pile of applications). If it reads something eles, you've got another problem altogether and should thank your lucky stars.
In the meantime, I guess I'll get back to sending out dozens of emails to the maintainers of our many, many affiliated Instagram accounts to explain the issue and try to get permissions, so provided we get approved by then, all our social media displays aren't broken during a huge event Saturday. Another option might be to use the OAuth-less json response available here, but that might break terms of service.
I have a solution to this. If you are using the same code I am, which appears likely. I was pulling the last two images using this.
https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3
What I did to get this working is the following.
Login to your Instragram account you are using as the application.
Go to the developer (API) area. https://www.instagram.com/developer/clients/manage/
Manage clients. Make sure your website URL is the same as your valid redirect URL.
Add new Sandbox User. Put in the account of the IG photos you want to reach.
Hit this URL: https://api.instagram.com/oauth/authorize/?client_id=CLIENTID&redirect_uri=REDIRECT_URI&response_type=token where the client ID is the same one you used in your previous app above.
You should get back and access token URL. Copy your access token.
Login as your account that you want the IG photos of. The account you added as a sandbox user and go to developer and approve the Sandbox Invites.
Change your original URL above from https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3 to https://api.instagram.com/v1/users/self/media/recent/?access_token=ACCESS_TOKEN with your access token.
This is the IG API Media endpoint documentation: https://www.instagram.com/developer/endpoints/users/
After that, it all worked for me and while you are in the sandbox, you should be able to pull the last 3 photos or at this point, figure out how to read the JSON to do so.
Has your app been approved after the June 1st Instagram platform changes?
http://developers.instagram.com/post/145262544121/instagram-platform-update-effective-june-1-2016
If you want to retrieve the user media file then try this, It's working for me
https://graph.instagram.com/me/media?fields=id,caption,media_url,media_type&access_token=ACCESS_TOKEN
For some reason the token is no more valid. Request it again.
Possible reasons why a token is no more valid:
changed password
verified the account
logged-in from a different country
I'm trying to set up various Instagram clients to use with website integration. I must say that I am extremely disappointed in the quality of the Instagram developer documentation, and their API has some seriously annoying aspects to it.
That being said, when I try to update one any of my clients (under any of three accounts), I get the following error (in a non-styled, blank page):
Sorry, an error occurred while processing this request.
What gives? I was able to update a few of my clients, but then started getting this error.
Also, why does Instagram make it nearly impossible to create more than five clients? I need more than this to cover all of the environments that the website(s) run in, so I've been forced to create multiple Instagram accounts for each site...
Apparently Instagram's API (or at least the part relating to adding/editing clients) was down. I guess I'll mark this as answered, but I really wish Instagram would offer better documentation/support...
Anyone else have this problem?
I cannot sign up for an Azure account.
On the registration page, it asks for your phone number and wants to confirm it by sending a text or calling you. I only have a Google Voice number, and I always get
We were unable to verify your account
No matter if I choose text or call. There is no way around it. Any help?
EDIT: Other posts have indicated it's a problem when your country isn't listed, but that is not the case here (I'm in the U.S.). Those posts suggest calling "your local Microsoft branch" but how do I find that?
.
After reading the comments above, and calling Microsoft myself, I was told the verification process does not support Google Voice or Skype phone numbers.
The person I spoke with on the pre-sales department of Azure said he could not manually create an account for me or validate my Google Voice number, despite me sending him this question on StackOverflow showing that others had been successful in calling Microsoft as I had.
My solution was to use a friend's number and have him send me the verification code he received. However, it must be within the Azure signup's session timeout period or the code is no good.
I really hope someone at Microsoft sees this and corrects it for future customers.
I wanted to throw in a answer for Republic Wireless users who are having this problem.
I know this doesn't pertain specifically to Republic Wireless, but this is for those users, and should perhaps prove helpful, since this is the 1st result from Google on the error message.
Republic Wireless is a VoIP company, but they still use an underlying sprint phone number to handle calls/texts when you are not under WiFi, here is how to access your underlying phone number so you can get past the Windows Azure registration verification:
Open the Phone app (the standard dialer that comes with the phone).
Dial ##786#.
The number shown for Mobile Number is your Sprint number.
Hit the Back or Home button to dismiss the information screen.
https://community.republicwireless.com/people/carlh/blog/2013/11/20/moto-x-how-to-find-out-your-phones-sprint-number
I faced this exact same error. After trying different solutions, i decided to change my browser from Google Chrome to Microsoft Edge - and i was able to verify my account thereafter