{ "id": "63049", "key": "TIMOB-2417", "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": "11229", "name": "Release 1.5.0 M04", "archived": true, "released": true, "releaseDate": "2010-12-06" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T03:19:12.000+0000", "created": "2011-04-15T03:19:10.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "defect", "facebook", "regression" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T19:28:03.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": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
1.5.0.91838a G2 (2.2), Droid1 (2.2) sim 2.1
\n1.Facebook > log in
\n2.Facebook > publish stream > tap publish stream button
Results: the button takes the press, but no action occurs for 3\nseconds or so, looking like the app is dead. the behavior at this\npoint is intermittant, it did work most of the time, but\noccasionally locked up on the droid1
Triage in M04, may not be problematic enough to warrant\n1.5.0.
I actually gave this a closer look than I probably should have\n(time-wise), given that we definitely won't change this sdk at all\nfor 1.5 (unless something simply doesn't work.)
\nThe delay occurs in FBDialog.loadUrl. (You can see the logcat\nwith timing info here. That code makes a complete, invisible\nPOST request before even popping up a webview -- I guess it does it\nin order to set a cookie (authorization) in the Cookie Manager\nbefore then showing the webview. After that's finished, it then\nfinally shows the webview and navigates to the special facebook\npage that lets you make the stream entry.
\nThis code all comes from a third-party SDK -- it's very brittle\nand we're replacing it hopefully soon via #2254.
What's the right approach ticket-wise? I would close this\ncompletely (\"invalid\" or something) rather than push it off to\nanother milestone, because I don't want to touch this third-party\nSDK -- i want to replace it. So in a sense I feel like we'll never\nactually try to make this code better/faster.
Assigning to Thomas for his opinion on disposition.
agree with Bill and marking as invalid. would be nice to have\n\"NOB\" (not our bug) for these issues. in the new bug base :)