In my iOS app, I am using the Alamofire library.
For all the post requests I am using in my app, I am seeing the same issue: most of the times it works, but sometimes(seems randomly) I am getting an error like this:
I wanted to debug this, so I activated CFNETWORK_DIAGNOSTICS(3) which gave me more info about the issue, but I am not able to see what is going wrong.
The console message when the httprequest fails:
The console message when the httprequest completes succesfully:
Could anyone help me out please?
Related
Please see the questions in atlassian community: https://community.atlassian.com/t5/Jira-questions/Jira-board-UI-is-not-loading/qaq-p/2239840
This one is kinda of duplicate in stackoverflow.
I have created new free trial Jira instance recently and my first project there. I am able to create issues there, but my boards like Backlog/Active sprints/Roadmap are not loading in UI. Please see the screenshot
screen1
The issue is not gone after a few hours. I have tested it on three browsers (Firefox, Chromium, Chrome) in both incognito and common modes. Also I have tested it on my phone in browser version. None of the above helped.
In the phone app by the way I am also not able to open issues with this error.
screen2
(not sure if these issues are related or not)
Could you please advise what could be the problem and how to fix it?
there are actually some warnings, errors and 4XX and 5XX responses.
Failed to run init function: TypeError: removeOldAnalytics is not a function function() { determineStorageKey(); setTimeout(bulkPublish, 500); removeOldAnalytics(); }
{"errorMessages":["Internal server error"],"errors":{}}
{"status":"Conflict","message":"User is not enrolled in message 'devops-launch-toolchain-spotlight'","errors":[]}
{"errorMessages":["Invalid request payload. Refer to the REST API documentation and try again."]}
Uncaught (in promise) TypeError: e is undefined
IndexedDB timed out.
{"errors":{},"errorMessages":["The property isDevopsProject does not exist."],"httpStatusCode":{"empty":false,"present":true}}
Source map error: Error: request failed with status 404
Source map error: Error: NetworkError when attempting to fetch resource.
screen3
screen4
I have tested 4 browsers, incognito modes, 2 laptops and 1 phone, my wifi and mobile internet, and nothing works. Same 4XX and 5XX error everywhere. I'm a bit desperate now since I have no clue what is the problem and how to fix it
I want to use the AdServices framework in my app but I keep getting an error.
I've added AdServices as a framework
I've imported it
I try calling let token = try AAAttribution.attributionToken()
When running on device, this fails with the internalError code, saying Error posting to Attribution server.
Why? Nowhere online explains why this could be or how to fix it. I'm running in debug mode, could it be that?
On the simulator it's even worse and can't generate a token, but I'm not too bothered about that.
I'm working on iPhone application using Appcelerator .Every thing in app working fine .but now one alert shows in this.
A quick google search should bring you to the list of error codes
(https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Miscellaneous/Foundation_Constants/index.html#//apple_ref/doc/constant_group/URL_Loading_System_Error_Codes)
In here, we can find the following
NSURLErrorServerCertificateUntrusted = -1202
Meaning that there seems to be a problem with the server certificates.
A quick search on this error gives us a possible cause:
The time of the phone might be wrong
(One of my iPhone users gets an NSURLErrorServerCertificateUntrusted error)
EDIT
I have no experience with appcelerator. This workaround is for native only, however, the idea should be the same.
And a workaround, if you were using NSUrlConnection:
Which makes use of
NSUrlConnection -connection:didReceiveAuthenticationChallenge:
HTTPS with NSURLConnection - NSURLErrorServerCertificateUntrusted
while posting, it is giving an error like "your message couldn't be sent because it includes content that other people on Facebook have reported as abusive" this thing is happening from today it self. Before it is worked fine with same code. I tried to resolve but no luck.
Can any body help me to resolve this thing!
]1
You can use the appeal form for blocked content.
What is the url that you are trying to share?
I'm trying to test in Dartium browser using the Geolocation API. In particular I try doing the following
window.navigator
.geolocation.getCurrentPosition()
..then((pos) {
window.alert(pos.toString());
})
..catchError((PositionError error) {
window.alert("Error code: ${error.code}, Error message: ${error.message}");
})
..whenComplete(() => window.alert("complete"))
;
Ignoring the fact I'm using window.alert here, All I get is an error with the following message "Error code: 2, Error message: Network location provider at 'https://www.googleapis.com/' : Returned error code 400."
However the same code works in Google Chrome when I use "pub serve". It also works with Firefox. How do I overcome this error, and get it to work in Dartium? Is it even possible?
UPDATE
I took a look at the 403 bug and tried using the fix specified on this page http://www.chromium.org/developers/how-tos/api-keys, and when I first tried this, I got my credentials and setting wrong, I was getting a 403 error, but once that was resolved, and all the APIs enabled, plus the environment settings of
GOOGLE_API_KEY
GOOGLE_DEFAULT_CLIENT_ID
GOOGLE_DEFAULT_CLIENT_SECRET
I was back to "Network location provider at 'https://www.googleapis.com/' : Returned error code 400.", so I conclude it isn't the same issue. Though if someone can prove me wrong, I'd be happy.
FURTHER UPDATE
This is a bug. I've answered my own question below.
Maybe you are running into this issue
Geolocation giving 403 error
Should be fixable by providing Google API keys for Dartium
This is a bug.
I posted this question on https://groups.google.com/a/dartlang.org/forum/#!topic/web/UMJHJlQH7wc, where Seth Ladd asked me to open a bug.
I've opened a bug for this, https://code.google.com/p/dart/issues/detail?id=15866. So hopefully this will be resolved soon.