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.
Related
I have recently been receiving the following error from 'cordova-plugin-advanced-http'.
{"status":-1,"error":"The operation couldn’t be completed. No space left on device"}
Using this plugin within my project, most of the time, all API calls are successful, however, sometimes, I receive this error message. Not on any particular API call either. I can't for the life of me figure out why nor have I found much online to narrow the problem down.
The project uses:
Ionic 6.19.1
Capacitor 3.5.1
Angular 13.3.8
I have recently updated all three frameworks because this problem was occurring on older versions too but updating them has not resolved the issue.
All devices using my project are iPads (IOS).
Has anyone come across this problem before, know why I am receiving this error, or know how to fix the issue?
Thank you in advance!
UPDATE
The device is printing the following error when a call fails with the above error code:
finished with error [28] Error Domain=NSPOSIXErrorDomain Code=28 "No space left on device" UserInfo={_NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask
Solution
Hey team - came across a similar post, where the answer solved my problem. Check it out if you're stuck on in similar situation:
https://forum.ionicframework.com/t/downloading-appflow-update-on-ios-gets-to-16-then-errors-with-the-operation-couldn-t-be-completed-no-space-left-on-device/222534
I am seeing the below error in iOS 13 when trying to setup an app with universal links. Has anyone seen this or know what it means?
I am seeing this error in the device console for the swcd process.
Error getting enterprise-managed associated domains data. If this device is not enterprise-managed, this is normal:
Error Domain=SWCErrorDomain Code=1701 "Failed to get associated domain data from ManagedConfiguration framework." UserInfo={NSDebugDescription=Failed to get associated domain data from ManagedConfiguration framework., Line=250, Function=<private>}
When I install the same app on an iOS 12 device it works perfectly fine. Any thoughts would be appreciated
It seems that upgrading to iOS 13.2.2 solves the issue.
There is no official confirmation about this, but is seems resolved on iOS 13.2.2.
There may be some different places that cause this problem. Note that the format of AASA file seems to be changed recently. Please refer to this.
If the delegate isn't called, and there are some Google Analysis or Firebase features in the app, then it may be caused by method swizzling. If that's the case, please refer to my answer here.
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.
I'm using AFNetworking to upload some content to server using AFHTTPRequestOperation. It is working good in iOS 7 but in case of iOS 8 mostly this call goes to failure.
I'm getting this error:
Code=-999 "The operation couldn’t be completed. (NSURLErrorDomain error -999.), NSErrorFailingURLKey.
Can you please help me to resolve this issue?
NSURLErrorDomain error -999 is NSURLErrorCancelled
You can review the error codes here
You might get this error due to a request timing out, or resubmitting the same request more than once. Without further code there isn't much to expand on, but have you ensured that you haven't lost your wifi settings since upgrading to iOS 8?
BTW you can use NSErrorFailingURLKey to find the failing URL - try putting it straight into Safari and see what happens
Your issue is being discussed here :
https://github.com/AFNetworking/AFNetworking/issues/2314
it seems to be related to keepalive implementation in iOS8, no solution available on client side for now, if you can configure the http server, disabling http keepalive should solve your issue ...
Today I decided to repackage, sign and publish my Android app to the Windows platform using the 'BlackBerry Packager for Android'. https://bdsc.webapps.blackberry.com/android/bpaa/app-signing-bar-creation
However it doesn't seem to work and I get the following error:
We're sorry, an error occurred while processing your request. The
information has been registered and we're working on getting this
fixed as soon as we can.
I have searched online and there seems to be no answer for this.
Has anyone experienced this issue or knows how I can resolve it?
Thanks a million,
Sarah.