{ "id": "62525", "key": "TIMOB-1893", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11225", "name": "Release 1.5.0", "archived": true, "released": true, "releaseDate": "2010-12-14" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T03:04:54.000+0000", "created": "2011-04-15T03:04:53.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "defect", "ios", "iphone", "rplist", "xhr" ], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T19:32:23.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}

on iOS 3 & iOS 4 when the device switches from wifi to\ncellular or vice versa the xhr call errors.

\n

see this ticket.
\nhttp://developer.appcelerator.com/helpdesk/view/43581

{html}", "attachment": [], "flagged": false, "summary": "XHR call fails after network switching", "creator": { "name": "ctredway1", "key": "ctredway1", "displayName": "ctredway", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "ctredway1", "key": "ctredway1", "displayName": "ctredway", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "126917", "author": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

There is a very good reason why this behaves the way it does,\nand the behavior is \"correct\" and something we have no control over\nas it happens at the system and hardware level.

\n

WiFi (en0) and data (some other device, I forget) are different\ninterfaces. Say that we have an HTTP request which starts on en0,\nwhich is then terminated. This means that the connection to the\nactual hardware interface has been terminated, which\nSHOULD be a cancel error. In addition, sometimes\nhardware is very bad about reporting its status as having the\nnetwork terminated. In particular, there's the following\nscenario:

\n\n

Here is what the user should do instead.

\n\n

Remember: When using HTTP, you are responsible for managing all\nof your connection information, up to and including monitoring for\nreachability changes.

{html}", "updateAuthor": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T03:04:54.000+0000", "updated": "2011-04-15T03:04:54.000+0000" }, { "id": "408483", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closed as invalid.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-03-02T19:32:23.000+0000", "updated": "2017-03-02T19:32:23.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }