You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PonyDebugger is connected in my app, and shows up on the list of devices (it's running in the simulator). When I click on it, (as in, the interface shows up, but no data at all, not even the attempts I made at logging).
If I open the web inspector, and have a look at the console, I see .
Request with id = 1 failed. unknown domain Debugger
and so on, all referencing InspectorBackend.js:237, which is in the reportProtocolError() method.
I'm initialising the debugger as follows in my AppDelegate:
As I said, in the XCode console I can see that it has connected, and in the pony gateway I can see the device listed, I just am not getting any data, and I have a feeling that the errors I posted a screenshot of above have something to do with it.
The text was updated successfully, but these errors were encountered:
Update:
I finally got some data from the PonyDebugger. The "unknown domain XXX" errors are responses from the iOS app and lists requestes Domains which are not activated on the app yet(or so it seems). When disabling and enabling networkDebugging, CoreDataDebugging, remoteLogging etc. the list of errors expands/shrinks.
PonyDebugger is connected in my app, and shows up on the list of devices (it's running in the simulator). When I click on it, (as in, the interface shows up, but no data at all, not even the attempts I made at logging).
If I open the web inspector, and have a look at the console, I see .
and so on, all referencing
InspectorBackend.js:237
, which is in thereportProtocolError()
method.I'm initialising the debugger as follows in my AppDelegate:
As I said, in the XCode console I can see that it has connected, and in the pony gateway I can see the device listed, I just am not getting any data, and I have a feeling that the errors I posted a screenshot of above have something to do with it.
The text was updated successfully, but these errors were encountered: