New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to attach to Ionic app running on iOS 12.3.1 real device #546
Comments
Hi @francescodoffizi and thanks for reaching us. Could you please describe your specific software versions? This information will be very helpful for us. Also, could you please clarify what kind of application do you use: Cordova or Ionic? Also, it will be helpful if you add information about iOS version that installed on your device.
|
Ionic projects (3 or 4 makes no difference as far as I can see) |
@SounD120 I did a test with a older Ionic 3.2 app and it works... so maybe the issue is ionic 4 related... |
@francescodoffizi looks like this is Ionic bug, because I couldn't even inspect Ionic app using Chrome. I've created an issue in Ionic tracker, so, I'd suggest you to subscribe to it to be posted as to it. |
Actual Behavior
Attaching to ios
Configuring debugging proxy
Unable to find target app webview, trying to fallback to the only running webview
Attaching to app.
'Runtime' domain was not foundError processing "attach": 'Runtime' domain was not found: [object Object] or 'Debugger' domain was not foundError processing "attach": 'Debugger' domain was not found: [object Object]
Expected Behavior
Software versions
Latest stable
Outputs (Include if relevant)
Attaching to ios
Configuring debugging proxy
Unable to find target app webview, trying to fallback to the only running webview
Attaching to app.
'Debugger' domain was not foundError processing "attach": 'Debugger' domain was not found: [object Object]
Output of the Cordova output channel (View -> Toggle Output -> Select Cordova in ListBox):
No Cordova entry in listbox
Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
The text was updated successfully, but these errors were encountered: