When I'm sending message with location co-ordinates through my Nokia 5800. I'm getting "Location request timed out" message. I am working in one project to accomplish this task. How can I solve this issue?? Any solution for this problem??
Related
I am uploading files to FirebaseStorage and i am getting this error on iOS :
Task <24E18897-20B7-45FD-9621-85FF09DC6326>.<1> finished with error [-1017] Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response" UserInfo={_kCFStreamErrorCodeKey=-1, _NSURLErrorFailingURLSessionTaskErrorKey=BackgroundUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"BackgroundUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>",
"LocalUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>"
), NSLocalizedDescription=cannot parse response, _kCFStreamErrorDomainKey=4, NSErrorFailingURLStringKey=https://firebasestorage.googleapis.com/v0/b/mybucket/o/user%2FNyq7dMqe1kcAZ77R1YwH5fsAkV83%2Fcontent%2F43aa2d41-7a19-11ec-bd39-85fcd9d025?uploadType=resumable&name=user%2FNqe1kcAZ77R1YwH5fsAkV83%2Fcontent%2F43aa2d41-7a19-11ec-bd39-8508fcd025&upload_id=ADPycdv0-OYZPx3zAGzLrn25ZdI9srgkgABHGKb_1fCqUO7AAPHsZTkz_iVX1NfuYQsn0LHgCCiOsSzhLiP4Ho7VynSf_ceJJw&upload_protocol=resumable, NSErrorFailingURLKey=https://firebasestorage.googleapis.com/v0/b/mybucket/o/user%2FNyqMqe1kcAZ77R1YwH5fsAkV83%2Fcontent%2F43aa2d41-7a19-11ec-bd39-8508fcd9d025?uploadType=resumable&name=user%2FNyq7dMqe1kcAZ77R1YwH5V83%2Fcontent%2F432d41-7a19-11ec-bd39-8508f9d025&upload_id=ADPycdv0-OYZPx3zAGzLrn25ZdI9srgkgABHGKb_1fCqUO7AAPHsZTkz_iVX1NfuYQsn0LHgCCiOsSzhLiP4Ho7VynSf_ceJJw&upload_protocol=resumable}
GTMSessionFetcher invoking fetch callbacks, data (null), error Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response" UserInfo={_kCFStreamErrorCodeKey=-1, _NSURLErrorFailingURLSessionTaskErrorKey=BackgroundUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"BackgroundUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>",
"LocalUploadTask <24E18897-20B7-45FD-9621-85FF09DC6326>.<1>"
), NSLocalizedDescription=cannot parse response, _kCFStreamErrorDomainKey=4, NSErrorFailingURLStringKey=https://firebasestorage.googleapis.com/v0/b/mybucket/o/users%2FNyq7dMqe1kcAZ77R1YwH5fsAkV83%2Fcontent%2F43aa2d41-7a19-11ec-bd39-8508fcd9d025?uploadType=resumable&name=users%2FNyq7dMqe1kcAZ77R1YwH5fsAkV83%2Fposts%2F43aa2d41-7a19-11ec-bd39-8508fcd9d025s&upload_id=ADPycdv0-OYZPx3zAGzLrn25ZdI9srgkgABHGKb_1fCqUO7AAPHsZTkz_iVX1NfuYQsn0LHgCCiOsSzhLiP4Ho7VynSf_ceJJw&upload_protocol=resumable, NSErrorFailingURLKey=https://firebasestorage.googleapis.com/v0/b/mybucket/o/user%2FNyq7dMqe1kcAZ77R1YwH5fsAkV83%2Fcontent%2F43aa2d41-7a19-11ec-bd39-8508fcd9d025-low_res?uploadType=resumable&name=user%2FNyq7dMqe1kcAZ77R1YwH5fsAkV83%2Fposts%2F43aa2d41-7a19-11ec-bd39-8508f&upload_id=ADPycdv0-OYZPx3zAGzLrn25ZdI9srgkgABHGKb_1fCqUO7AAPHsZTkz_iVX1NfuYQsn0LHgCCiOsSzhLiP4Ho7VynSf_ceJJw&upload_protocol=resumable}
This result in a [firebase_storage/unknown] An unknown error occurred, please check the server response.
But this time i can see the iOS failure, not the server response unfortunately...
So what does Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response" mean and how to fix it please ?
Note : I have seen this question but it's not really something i can fix myself as i am using the Firebase iOS SDK...
EDIT :
I have opened an issue and a case in Firebase Support to get more information about this as no one seem to have some for now unfortunately.
This is probably a bug server-side as i can't reproduce it 100% of the time and the error is also not useful for debug.
EDIT 2 :
Firebase support was able to reproduce this issue with quite low internet connections, but in my case this happens also with normal connectivity.
I have also set the metadata specifying the content-type to avoid an extra "parsing" server side but it didn't change anything unfortunately.
I have same problem.
But I got it why occured this problem.
Maybe,this problem is occured by weakly network level.
If you want to reproduce this problem,Please Use "Network Link Conditioner.prefPane" in "Hardware" of "Additional tools for Xcode"
Additional tools for Xcode Download link
I could reproduce below settings.
Downlink Bandwidth: 10 Kbps
Downlink Packets Dropped: 5 %
Downlink Delay: 440 ms
Uplink Bandwidth: 10 Kbps
Uplink Packets Dropped: 5 %
Uplink Delay: 440 ms
DNS Delay: NO SET VALUE
It setting could add by manage profiles.
Good Luck, and I apporogy my English.
Today I started receiving errors from Facebook when my app tries to post a message.
The app successfully authorised, Facebook message window pops up, everything looks fine (links, pics, description) , but when I press post. it times out with this message
Encountered an error while processing the request: 502 Error parsing server response. Got EOF while waiting for outstanding responses Please try resending your request. This is probably not a bug in proxygen. Based on experience, either intern or latest is temporarily down due to a SEV or push. Please check in e FYI or #e first. If the error persists through retries, or if you have good reason to suspect this is a bug in proxygen, please report the issue to ti-bugs#lists or #ti with the following debug information: 2012-05-20 22:24:40 slb010.02.snc5 1585267068836963531
UPDATE: It is a Facebook issue. There is an opened and assigned bug report here You can subscribe there to follow the process.
It looks like Facebook fixed the issue. My apps work fine.
If you still experience the same problem, you can check out the progress here: http://developers.facebook.com/bugs/411849912170144?browse=search_4fb9fb43db2468a28526107
If this issue comes up again check whether there is an already submitted bug here: http://developers.facebook.com/bugs/ if there isn't submit one
I use LinkedIn-iPhone API to update LinkedIn status, which worked for several times, but most times it does not work well, and it has never worked for the last 5 days. I don't know whether it is the problem of the LinkedIn web site or API connections.
The console log:
++ LinkedIn engine reports failure for connection
98A66D65-A8EB-4ADF-9B03-76EA54AE5DAE
The operation couldn’t be completed.
(HTTP error 400.), error: Error
Domain=HTTP Code=400 "The operation
couldn’t be completed. (HTTP error
400.)"
Is the error from the unstable LinkedIn API? or my code?
Silly me, I found the problem of HTTP error 400, which means: Duplicate updates. I changed the message for updating then it works fine.
Not sure whether moderator should delete this post or not? or how do I close it?
I get this error when I try to call a PIWIK API.
Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Cookie: piwik_visitor2=1%3DMjQ2NzVkZWQzNWE2NmVmZTg0MDAzYjcxNDVjMWNkYjM%3D%3A2%3....
How can I get ride of this. Piwik is hosted on one of our server. Is there anything to do with Apache config?
By the way, it has been working for quite a while. But it has suddenly stopped working.
Please advise.
Thanks,
Imran
This is a known bug in Piwik, that will be fixed at some point in the future: http://dev.piwik.org/trac/ticket/409
However as per info in the ticket, the team will release a fix to stop causing the error for 1.0, in next weeks probably.
I am using MGTwitterEngine for iPhone to support twitter, I am getting error(403) while posting a message second time how to handle this issue.
That is.. Let the message is "what are you doing" I am posting using [mTwitterEngine sendUpdate:"what are you doing"] for first time it is posted successfully, if i want to post the same message again it is throwing 403 error.
How to handle this?
Can i put the alert "Duplicate message" if error no 403? Is 403 error for duplicate messages only?
Added : Is it possible to check if an message is already posted in MGTwitterEngine?
The 403 error is not only for duplicate message so that you cannot throw the error message to user.
http://developer.twitter.com/pages/responses_errors
You have to find the duplicate message in your application code by keeping the last updated message.