[BackGround]
I am using Fiddler4 on Windows and see iPhone HTTP traffic.
I open a third-party app which I want to inspect the API response.
[Problem]
I got the HTTP traffic(see the image below) after opening an app.
Seems I got an error from Host graph.facebook.com.
Actually the app hang up and showing loading but not going to show any page.
If Im not using Fiddler, I can see the market place page.
[What I want to do]
I want to avoid the error and would like to continue the app and check other API's response.
How can I achieve that ?
enter image description here
Related
I’m currently developing a music service and testing it via customsd. The integration in the controller app is working (iOS App & Windows Desktop App) - so I can browse - but I can’t get a Player to play any track. I keep receiving ‘unable to connect’ errors once I hit the ‘Play’ button in the controller. I can see on the service side that the Player sends a getMetadata and a getMediaURI request, and the SOAP responses delivered by the service are identical to working examples from another source; however, the Player seems unable to process them. I am kind of stuck, and I guess what would help me are the Player logs. Is there any way to get them?
Or, does anyone have any other idea about the root cause of the issue?
EDIT: More or less accidentally, I came across the reason of my problem. Whereas in general, Sonos can handle arbitrary IDs, getMediaURI only seems to work when it requests the URI for an ID of the form track:something. I don‘t remember seeing this as a requirement on the developer pages.
Anyway, got it working now.
If you're getting a getMediaURI request and responding to it with a valid response, then most likely the player is failing to process the media file itself. Are you seeing the media file being downloaded? You could host the media file locally and include the URI to that in the getMediaURI response to check.
Note that the <mimeType> included in the metadata is used to inform the player of the type of media the URI in the getMediaURL response points to.
So if you were to return <mimeType>audio/ogg</mimeType> for track123, but getMediaURI's response contained the URI https://something.xyz/track123.mp3, playback would likely fail due to the mismatch.
Have you seen bonob? Someone made a music service emulator for navidrome (self-hosted music library, a la spotify). It should be a great resource to get you started.
He wrote that your music service has to be available at https for it to even start functioning.
Note, I'm the developer of sonos-ts a library to control sonos speakers from typescript and node. And the external music services are documented here
I've deployed a React Redux site on hostgator.com. While it works to visit the page and navigate as usual. (React routing works), it shows 404 not found whenever I reload the page.
I talked to their support which, before leaving 20 sec into the conversation, came with the suggestion that it may have to do with the site trying to run on https, while no SSL is implemented.
I'm curious, why does it work locally and not on the world wide web? Any thoughts?
Thanks.
You need to look into a Server Side Rendering solution. A good framework for doing so with React is Next.js.
Basically as long as you don't refresh the page React-Router has control over the address bar as well as history via the History API. But when you hit refresh you send a request to the server for whatever is in the address bar. But the server is not handling your routing, React-Router is on the client side. You also won't be able to type a child route directly into the address bar without server side rendering.
I have a problem with BigCommerce installation process.
According to documentation (https://developer.bigcommerce.com/api/callback) I receive GET request, do exchange for OAuth info via POST request and return HTML page to user.
App seems successfully installed, I can see it in left panel, but it don't send request to LoadCallback with signed payload. When I click to application's icon it just hides/shows HTML page that I send during intallation.
Seems like the only way to make BigCommerce do LoadCallback request is to open app after relogin.
Did I do something wrong during installation process?
No, this is intended behavior. Most apps have a sign up process that cause a frame reload of the app. You can force a reload after installation or use a form submission action via javascript. Alternatively, you can reload the control panel and reopen app or relogin and open.
I am trying to create a Google+ hangout app.
I set up all fields in Google API console Enabled the Google+ hangout to my API's. When I am trying to add my hangout app to my hangout video call.
I am getting error like
There was an error loading your app! This app did not load because
there appears to be something wrong with it.
my XML source file is here
When my hangout app trying to download in hangout, my rails server getting error like
ERROR bad Request-Line `\x16\x03\x01\x00�\x01\x00\x00�\x03\x03y\bA黉̉EI�\x02\x06�p4�B8t\a�?붜��\x12�'.<br/>
ERROR bad URI `��T��\x15d"�\x0F��䃠\x7F�W'�Y�P�=\x00\x00\x1E�'
can anyone help me to come out of these.
when server asking for localhost:3000/demohangoutapp.html , in browser network tab the URL header contains Request URL: "https://localhost:3000/demohangoutapp.html?parent=https%3A%2F%2Fg7vvv07ifja6kfh7hlbpuen02gi410ue-a-hangout-opensocial.googleusercontent.com%2Fgadgets%2Fifr%3Furl%3Dapp%253A%252F%252F1089532940946%252Fhangout%26container%3Dhangout%26view%3Ddefault%26lang%3Dall%26country%3DALL%26debug%3D0%26nocache%3D1%26sanitize%3D0%26v%3De9f67d65d3c45721%26testmode%3D0%26parent%3Dhttps%253A%252F%252Fplus.google.com%26mid%3D1%26authuser%3D0%26hl%3Den%23st%3De%253DABul2V3342qYiNrtSKZaSOoxnVJcmjYLxlJqb%25252Btr8Am84%25252BAj6kYeDXuwqhkxsc5gE64NMBK9CbLIe77j9bOYVgOG9p9z24qCc4Pg6E3usS1oDG%25252F16daISnblUWzGg7XMSklgB5cfXZ2P%2526c%253Dhangout%26view-params%3D%257B%2522applicationUrl%2522%253A%2522https%253A%252F%252Fhangoutiframer.appspot.com%252Fforward%252Fv0.2%253Fu%253Dhttps%253A%252F%252Flocalhost%253A3000%252Fdemohangoutapp.html%2522%252C%2522appData%2522%253A%2522Hangouts%2522%257D&token=ya29.VQGN9n0LHGvwCD0CpORWgLMF3XX7xaExyl7mD_WjtcLbT4ie9uxFW9eIrPsYmRDxHebwSTs-RkGOHQ&gd=Hangouts" and response is failed to load
Looking at your source the issue is that your link to the Hangouts API JS is wrong/outdated.
The currently valid link is https://plus.google.com/hangouts/_/api/v1/hangout.js
Changing this link should fix the issue.
I want to control a mac app via a local website. I think the best way is to create a webserver with my mac app and then to send (primarily) integer values from the website and vice versa.
I found already CocoaHTTPServer, but I'm not sure how to do it.
For start with I want to have a slider on the website, that updates a slider in my mac application (and vice versa)
You will initiate on a separate thread or operation the web server and always wait for incoming requests. Whenever you receive a request you will handle it accordingly.
Also, if you are using this: https://github.com/robbiehanson/CocoaHTTPServer/
then there are a few examples that show how to do it. Copy the code from there to begin with the web server handling requests. After that, think through what you want to send and what you want to do. Build a form or something for the web site and submit a request to the web server.
CocoaHTTPServer will let you embed the web server into your application, which is a fine solution for what you're trying to accomplish.
Some thoughts on how to engineer it:
You'll need to subclass HTTPConnection.
Model your solution on the PostHTTPServer example.
You could get the data you want to send into the URL. Something like POST http://localhost:12345/updateSlider/123. (You probably don't need an actual POST, but no reason it wouldn't work. Technically a PUT would be more correct.)
Start by handling that part – where the browser sends a value to your application. To generate POST/PUT requests for testing purposes, use curl, or else build a static page and open it in your browser.
When you get that working, then worry about presenting a web page to the user.