WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
173593
Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service
https://bugs.webkit.org/show_bug.cgi?id=173593
Summary
Could not signal service com.apple.WebKit.Networking: 113: Could not find spe...
Ievgen Gavrysh
Reported
2017-06-20 05:29:40 PDT
Hi, I am using WKWebView from WebKit library for my iOS app(iOS v. 8.0). I am loading html to a newly created WKWebView control by calling -loadHTMLString:baseURL: method. * Within 30 sec after page is loaded I receive a following error: Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service, sometimes I receive this message twice. Can you please advice what does 113 code means? How can I fix it? Also I have tried switching to iOS v.10 and the problem persists. Tried clearing cookies etc - nothing helps to solve this problem, it even happens if I load blank HTMLString, so clearly this is a configuration issue. Do you have any idea why does it happen? * Are there any list of all possible WKWebView error codes with explanations? Thanks for your work. Hope this question will be at least partially answered:) due to its vague structure...
Attachments
Add attachment
proposed patch, testcase, etc.
Brady Eidson
Comment 1
2017-06-20 15:21:55 PDT
There would be no meaningful reason to explore an issue that presents on iOS 8.0 at this point. iOS 10.3 has a substantially different WebKit than iOS 10.0, so if you're unwilling/unable to try iOS 11 developer preview, 10.3 would be a bare minimum.
> Hope this question will be at least partially answered:) due to its vague structure...
You're right, the structure is vague. There's too many variables at play for us to know what you're experiencing. The best way to get a bug diagnosed is to attach a test case that shows the issue; a reduced app would be great.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug