iOS11 devices are occasionally issue this error: "HTTP load failed (error code: -1005 [1:54])."
The app is connecting to https json web service and while its in the foreground everything runs smoothly (timer is doing the web service calls), but from time to time (cannot replicate the issue all the time) this error occurs when the app is moving from background to foreground.
Whenever app is moving to background I invalidate the timer performing the calls, and whenever app is brought to foreground the timer is initialised again - everything runs smoothly most of the time.
My JSON parsing function says no data has been received.
Cannot replicate this issue in Simulator.
ATS is allowing Arbitrary Loads and I've also configured my domain as Exception Domain.
Using XCode9.3 and iPhones with iOS11 and up, and no clue what might be causing this.
--- update ---
I also find these errors usually nearby the error mentioned earlier:
"dnssd_clientstub read_all(6) DEFUNCT"
"nw_resolver_create_dns_service_locked DNSServiceCreateDelegateConnection failed: ServiceNotRunning(-65563)"
--- end of update ---
Thank you in advance.
BR, JC
Related
I am trying to pass the virtual reallity checks in order to publish an App on the Oculus Store, but unfortunatelly I get the test "TestSubmitFramesWhenInDash" failed.
Starting TestSubmitFramesWhenInDash
Waiting for the application to run for 5 seconds before testing begins...
Starting test...
Testing for focus aware app.
Showing dash...
Number of texture swap chains committed when visible 0
Number of texture swap chains committed when not visible 0
ERROR: Focus aware app failed to commit to texture swap chain when dash was shown.
Please refer to VRC Guidelines: https://developer.oculus.com/distribute/latest/concepts/vrc-pc-input-9/
Cleaning up...
Test FAILED
What can I do to pass this test?
I was getting this issue using the Oculus Integration package that comes with Unity,
I moved to the "Oculus XR Plugin", but got other tests failed like "TestSubmitFramesWhenNotVisible" or "TestAppShouldQuit",
but I found that the results of the "VRC Validator" are not so accurate,
then I submitted the App for review and passed the test.
My App was published without any problem.
So we use Selenium in C# to control Chrome. The following problem has occurred both in Chrome v74 with the v74 chromedriver and in Chrome v75 (the beta) with the v75 chromedriver.
After about 12 interactions with the website we get an error, for example
[10084:5660:0601/111205.119:ERROR:browser_process_sub_thread.cc(221)] Waited 57 ms for network service
We're not in a position to edit browser_process_sub_thread.cc and recompile.
I have searched for help on this issue and it is being discussed elsewhere. However, nothing much seems to be happening as the v75 beta breaks with the same issue.
How do we get around this problem? It only appears on this set of tests and not on others.
LATER
Now I'm getting this kind of message, viz
ERROR:browser_process_sub_thread.cc(217)] Waited 285 ms for network service
immediately rather than after some interactions! What's happening?
This error message...
ERROR:browser_process_sub_thread.cc(217)] Waited 771 ms for network service
...is coming from the IOThreadCleanUp() method within the browser_process_sub_thread.cc file which is implemented as:
// Record time spent for the method call.
base::TimeDelta network_wait_time = base::TimeTicks::Now() - start_time;
UMA_HISTOGRAM_TIMES("NetworkService.ShutdownTime", network_wait_time);
LOG(ERROR) << "Waited " << network_wait_time.InMilliseconds()
<< " ms for network service";
As per the discussion in Chromium Servicification - Need better handling for when a core service process fails to start/initialize following the new Network Process (NP) [--enable-features=NetworkService] if a child process is spawned but the service startup fails, in those cases:
google-chrome browser UI remains visible and open.
As the service is restartable, it appears an infinite loop of attempted child respawns is happening under the hood, which consumes more system resources.
The visible browser does not appropriately shutdown due to critical failure and just sits there with no networking under the hood.
So a strategy was necessary for all the core services those needed by Chrome to have running, possibly a failure path for the Network Processes (NP).
Following the above mentioned requirement, as per the discussion Sandbox the network service on Windows Chrome introduced the new sandbox (SANDBOX_NETWORK_TYPE) for the new Network Process (NP).
Windows is the first platform to roll out of both the new features and you are one of the luckiest user to have the first hand user experience of:
Feature to enable for network service: NetworkService
--enable-features=NetworkService
Feature to enable for the windows sandbox on the network service: NetworkServiceWindowsSandbox
--enable-features=NetworkServiceWindowsSandbox
This revision and this commit with in sandbox_win.cc from #WillHarris when lands up will address this issue.
Developed an app using Xamarin.Android that periodically sends the location of the device through an API rest.
I randomly receive the following message in the UI: "My app is not responding, would you like to close it?"
I would like to know how to intercept the cause since I can not intercept it at development time.
Thank you.
Adding a crash reporter will definitely help you get to the bottom of your issue. Is there a chance that you are calling the REST service from the UI thread? If so, then if there is a network delay, it could "hang" the UI thread, this will result in Android killing the process because it thinks it is no longer working. To get around this issue use:
Task.Run(() => CallYourRESTService());
That way your UI thread won't be locked up. Just a suggestion. Of course it's hard to say without seeing a code sample.
As can be seen in the title, when I run the example of physiJS (from github repo) it show only background, fps counter, but no physiJS functionality at all (pure three.js works fine). When I run on the: http://chandlerprall.github.io/Physijs/examples/vehicle.html everything runs ok. I have no idea right now where to start looking and where the problem is. Any ideas of what the cause could be?
PhysiJS uses a web worker to run the updating functionality, and web workers are not allowed on local systems as they require the loading of additional resources through JavaScript (and this is not allowed by cross-origin policies on some browsers). It's related to your browser, on my mac Safari allows it, but Chrome throws an error:
Uncaught SecurityError: Failed to construct 'Worker': Script at 'file://physijs_worker.js' cannot be accessed from origin 'null'.
The worker is required to run PhysiJS, so you should use a local server like MAMP to test it on your local machine.
I have an app deployed on meteor.com, which after 2-5 days of working perfectly suddenly becomes unresponsive to requests. Restarting the app by deploying it again causes it to work properly.
What's the best way to debug this? I don't know how to reproduce the issue on my local server since it only happens intermittently.
Nothing seemed off in meteor logs other than this line:
spiderable: phantomjs failed: { [Error: Command failed: ] killed: true, code: null, signal: 'SIGTERM' } stderr:
I tried removing the spiderable smart package and the issue still occurs.
Meteor.com's hosting via meteor deploy will kill your app if its not visited for somewhere near 2-4 hours.
This doesn't mean that its dead though, if you load it up in your web browser it'll take a couple of seconds extra to get running again. It might take longer if you have a heavy startup load, though.
Meteor hasn't brought up details of its paid solutions yet, but if you want to keep your site up for longer it should automatically if it has a visit every hour or two. I'm not suggesting that its the best way to do it, but you could remotely ping it too.