Worklight 6.2 building a hybrid application targeting iPad - we get the symptoms described below in the xCode Simulator irrespective of exactly which target device we select.
The application currently attempts a call to
WL.Client.login()
from within wlCommoninit()
Our target server is a full WL Server running on a Liberty instance on a remote machine, we use HTTPS and a specified IP Address
https://w.x.y.z:443/worklight
We have adjusted the Deploy Target and rebuilt the app before running XCode.
The WL.Client.login() error callback fires and we see log messages indicating that we are attempting to hit the correct URL. We also see this error message
NSURLErrorDomain error -1012
We do have a complex network setup, with a firewall between the iOS simulator and the server and yet if we run up Safari on the simulated device we can correctly access the URL.
Questions:
Does that NSURLErrorDomain reflect the cause of the failure? Or is it just part of the error processing?
Any suggestions for further diagnosis?
Further investigation indicated that we did have the wrong URL configured. It seems that
NSURLErrorDomain error -1012
is not in itself an indicator of the problem. Rather, the error follows from the failure to reach the specified host. Conclusion: study the logs prior top that NSURLErrorDomain message.
Related
I'm trying to upload an image to storage emulator locally from iOS simulator (the same thing works without issues on Android):
This is the error:
WARNING: Unable to set the Firebase Storage emulator settings. These must be set before any usages of Firebase Storage. If you see this log after a hot reload/restart you can safely ignore it.
[VERBOSE-2:ui_dart_state.cc(198)] Unhandled Exception: [firebase_storage/unknown] An unknown error occurred, please check the server response
It isn't much to work with.. I searched everywhere and found no working solutions. There seems to be similar issue that was related to connecting to production storage.
But this still doesn't work for me on local emulator.
I have stoppped appium server and then I tried to capture object through UIAutomatorViewer, but still it throws the error as "Unexpected error while obtaining UI Hierarchy". I have tried the following options.
Stop Appium server in the background.
Disconnected mobile device & connect it back.
3.close the uiautomatorviewer.bat file & restart it again.
Restarted the device
a. Turn on USB DEBUGGING
b. Enable view attribute inspection
c. Select the debug app option and choose io.appium.uiautomator2.server
adb devices to recognise my device.
I have exit and restarted uiautomatorviewer
After tried all the above options, still I get the same error.
Please help to get this issue resolved.
UIAutomatorviewer Error
We have a game in Unity 5.6.1f that uses Firebase Remote Config. Everything works fine on our devices, but after release we are noticing a lot of errors sent from player devices to our error reporting system. Problem occurs only on iOS.
Remote Config: Fetch encountered an error: The operation couldn’t be completed. (com.google.remoteconfig.ErrorDomain error 8003.)
I can't find a solution anywhere. Thanks!
According to the documentation the error 8003 is defined as
FIRRemoteConfigErrorInternalError = 8003
So the issue is probably not on your side.
Added this so it might help someone in the future.
Like #jd291 said, 8003 documentation seems to point to backend problem:
/// Internal error that covers all internal HTTP errors.
FIRRemoteConfigErrorInternalError = 8003,
This problem also occurs if you haven't published your configs on firebase yet.
I sometimes start to get the following error
2017-04-02 18:55:22.645937+0200 Stamps[730:111791] Connection peer
refused channel request for
"dtxproxy:XCTestDriverInterface:XCTestManager_IDEInterface"; channel
canceled Failed to run tests: The operation
couldn’t be completed. (DTXProxyChannel error 1.)
Last time, when this happened, I just did some random actions with clean my project, remove derived data etc., and it was fixed. Now, it happens again - just after a start of the app, it closes and log contains this error.
What does it mean and is there any workaround here?
I use XCode 8.3, Swift 3.1, test on device 6s with 10.3 installed.
Surprisingly, to fix this, I just replugged my iPhone to another port
I'm working on sending message through UDP. However, I've been trapped in the problem about 'binding port'.
When I built the project on iOS simulator first time, nothing strange happened. Everything was fine.
But when I built the project second time. I got an error message from terminal when the app tried to bind port.
The message goes like this "Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo=0x767c830 {NSLocalizedFailureReason=Error in bind() function, NSLocalizedDescription=Address already in use}"
What's confuses me is that the error didn't appear when I run my app on iPad.
I guess that maybe it is for the reason that I didn't close the socket. But why it goes correctly on iPad？
Hope someone could solve this. Thx!
Current head of GDAAsyncUdpSocket does not (also) set SO_REUSEPORT (it just does ADDRESS, which is quite enough for TCP).
I just popped in a quick fix:
https://github.com/dirkx/CocoaAsyncSocket/commit/5ec8c83d59ecb754824f706198eb62e29961c1be
https://github.com/dirkx/CocoaAsyncSocket
and it should get fixed upstream too:
https://github.com/robbiehanson/CocoaAsyncSocket/pull/159
Thanks,
Dw.