With apps enabled and track set to public, the track will not load and just return a blank page:
https://api.soundcloud.com/tracks/123737611/stream?client_id=9f9f3e2d2545c59bab31a850ca4191b3
The soundcloud page I'm trying to stream from is here: https://soundcloud.com/capital-cities
Any idea why this is happening?
Bug, as referenced in other StackOverflow posts.
Has not been acknowledged, and still no reply on an email sent out to them.
SoundCloud API Streaming fail blank page
Getting a 404 page for the stream_url. All permissions are set
Email sent Thu, Jan 2, 2014. No reply.
Related
I have an issue with my Spring-Boot based, web-application and mobile browsers behaving very strange when a link in Gmail is selected.
The valid flow, which works on most devices and browsers (on iOS, Android, OSX, etc.):
User clicks on a link in the Gmail application.
User is asked which browser the link should be opened in, selects Chrome.
GET /path-01 - results in 302 to /path-02 and Set-Cookie header with JSESSIONID=01.
GET /path-02 - results in 200 and a session with ID 01 is restored.
The invalid flow, which appears sometimes on iOS 13 with Chrome version: 81.0.4044.124 and supposedly on Safari browser and even on Android with Chrome browser (sadly, I was not able to determine versions for any of them):
User clicks on a link in the Gmail application.
User is asked which browser the link should be opened in, selects Chrome.
GET /path-01 - results in 302 to /path-02 and Set-Cookie header with JSESSIONID=01.
GET /path-01 - results in 302 to /path-02 and Set-Cookie header with JSESSIONID=02.
GET /path-02 - results in 200 and Set-Cookie header with JSESSIONID=03 because there were no Cookies sent along the request.
GET /path-02 - results in 200 and Set-Cookie header with JSESSIONID=04 because there were no Cookies sent along the request.
This odd behavior with double requests and no Cookies being sent after a redirect are causing my flow to break because /path-02 expects a value in session which is not there since a new one has been created. The invalid flow appears only sometimes, which is also frustrating. So far I have not found any relation of why is that so.
I have also experimented with the SameSite attribute being set to each of the possible values and invalid flow appears sometimes on each of these settings anyway.
It is also worth mentioning that after clicking on a link in Gmail, a user is being redirected through https://www.google.com/url?q=https://example.com/path-01&source=gmail&ust=1588944764533000&usg=AFQoCNECXqm1HdH9o66Iu1wD_VnOPE6Q6p.
Update
The issue presents itself when there is another card with the URL to the same site, but different path, already open. Then, when a user taps a link in Gmail, the browser opens and the card in the background also seem to go to the same URL the second one goes to and additionally no cookies are sent for both of those requests. The issue can only be reproduced on iOS, on both Chrome and Safari browsers.
Using Javascript + jquery Fetch I was able to search using the YouTube API - then it stopped working and now I get error 403 telling me
Access Not Configured. YouTube Data API has not been used in project 482017898664 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=482017898664 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry
However when I go to that address my API IS ENABLED. And I can run a search from https://developers.google.com/apis-explorer/#p/youtube/v3/.
Why has this stopped working and how do I get it to work again since its saying my API IS ENABLED.
NOTE - "wait a few minutes for the action to propagate to our systems and retry" - I've waited 3 days and its still not working.
I had the same issue. This is because youtube disabled your project's access to Youtube data.
Two things you can check if that's really what happened to you.
You should receive an email from Youtube with subject
[FYI] Youtube disabled your inactive project's data API service
Your Queries per day in the quota page was set to 0. (and you are not allowed to edit it)
The only way to get your access back for the same project is to fill up this form and wait for their action.
I'm trying to integrate Instagram login into my app to get the logged in user's details, I've registered my app on Instagram and got my client ID, then I added a new URL Type in the project settings with the identifier: igxxxx (where xxxx is my client id), i've also set the redirect URI to be (xxxx://authorize), once I successfully log in (using a webView) Instagram displays a white blank page with (400 Bad Request) text written on top, however, when I change the redirect URI to anything else, it opens without problems after a successful login.
how can I redirect the user to the app after he logs in with Instagram.
p.s. I use this library to ease up things.
thanks in advance.
Here's what I have found so far. I have been able to resolve the issue to get the app to work on the iPhone. However, this solution doesn't allow me to submit the app on the app store as you will read ahead. I have submitted a bug with instagram, not sure how long they will take.
I would suggest everyone go to this link and "Report Issue":
https://www.instagram.com/developer/clients/manage/
I have had an app in app store for couple months without problems.
However, since June 19, all the users trying to authenticate get a white page with "400 Bad Request" after they login with their IG account.
The issue is very common as you will see on this stack overflow page:
Instagram API prevents redirection to iOS app upon successful login with 400 bad request error
And google shows the same issue with many users since June 19.
I have figured out that the old redirect URI which we were using:
myappname://
is the issue.
If we change this redirect URI to:
http://myappname
or
https://myappname
This all starts working fine and we get the access token.
However as per RFC1738, this is not a valid format for URL schemes which is used in iOS development.
So we get error when submitting our apps to app store:
ERROR ITMS-90158: "The following URL schemes found in your app are not in the correct format: [https: //myappname]. URL schemes need to begin with an alphabetic character, and be comprised of alphanumeric characters, the period, the hyphen or the plus sign only. Please see RFC1738 for more detail."
ERROR ITMS-90158: "The following URL schemes found in your app are not in the correct format: [https: //myappname]. URL schemes need to begin with an alphabetic character, and be comprised of alphanumeric characters, the period, the hyphen or the plus sign only. Please see RFC1738 for more detail."
So we can't submit to app store with this solution.
So unless instagram does something to fix this back to how it used to be, we are stuck :(
I always get this message "Please visit http://bit.ly/instacomments for commenting access" when I use the endpoint /media/media-id/comments (see http://instagram.com/developer/endpoints/comments/) to post a comment to a friend's post in my iOS app, I requested these scopes from Instagram: scope=likes+comments+relationships.
I visited the web page mentioned in the error message and filled the form, months ago and not only once, but no lucky.
I also sent email to apidevelopers[at]instagram.com for access, still no lucky, and no response.
Anybody knows what w should I do?
You have to make a request to Instagram to get access to posting comments through the API. The email address is in the developer documentation. If you follow the link you are receiving in the error, it will take you to the page to request access.
I've recently enabled the Facebook Open Graph stuff on my web app (so and so has just read this and that on here and there). Now I post the request to Facebook when a user posts something, as part of the page load in the controller. The problem is I receive the following error:
HTTP 500: Response body: {"error":{"type":"Exception","message":"Could
not retrieve data from URL."}}
My first thought is that the open request to load the page is blocking any FB scraping of OG information, as it seems after it's been cached I no longer receive this error.
Is this likely? If so, what's the best way to work around it?
WHY THIS HAPPENS:
I had this same problem today, and it is because your Koala script (assuming you're using koala - if not, you should try it out because it's great) sends its request to Facebook before your URL is up. This means that when Facebook registers the post, it comes to the URL you specified to pick up the meta tags. Unfortunately, the page itself hasn't been loaded yet, giving it a 500 error
HOW TO SOLVE IT:
Use the delayed_job gem to prevent your post call from occurring before the page loads, which allows facebook to scrape your metatags correctly.
FOR EXAMPLE:
def post_to_facebook([ACCESS_TOKEN])
graph = Koala::Facebook::API.new([ACCESS TOKEN])
graph.put_connections("me", "[APP NAMESPACE]:[ACTION]", :[OBJECT TYPE] => [OBJECT_URL])
end
handle_asynchronously :post_to_facebook