{ "id": "62621", "key": "TIMOB-1989", "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": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:57:45.000+0000", "created": "2011-04-15T03:07:28.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "defect", "facebook", "rplist" ], "versions": [], "issuelinks": [], "assignee": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "updated": "2011-04-17T01:57:45.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}
Fail case is to be seen also in our KitchenSink. Go to Mashups -\nFacebook - Publish Stream (or Publish Status). Do a Facebook status\nupdate and you should get an alert dialog after you are finished,\nbut you don't. The facebook update occurs as planned, but the alert\n-- which should tell you \"Your status was published\" -- is\ngenerated from inside the callback function, which never fires.
(from [671ca48045584277d384bd5f3203ca9b40e73848])\n[#1989] Check for requestCode instead of\nresultCode when finding callbacks. Now callbacks occur, but the\nproblem is the result code is always 0 which sets success to false.\n\nhttp://github.com/appcelerator/titanium_mobile/commit/671ca48045584...
So i got the callback to fire, but it always thinks that\nsuccess
is false
.
(from [caff4cd3e2c8a70e76d6b9c8a3c67f39ac2af888])\n[#1989] Recent change to compiler.py made\nactivity and permission detection fail. After discussing with\nmarshall, taking out that change so Facebook activity gets put\nsuccessfully into AndroidManifest. \nhttp://github.com/appcelerator/titanium_mobile/commit/caff4cd3e2c8a...
(from [4b3b3d5e03e98363198532c0d62e52568f024476])\n[#1989] Put the facebook success/cancel urls\nin GET params instead of POST-- now the activity accurately sets\nthe result. \nhttp://github.com/appcelerator/titanium_mobile/commit/4b3b3d5e03e98...
(from [f3bf1945838339091296179fd2179913d11165c3])\n[#1989] Put the facebook success/cancel urls\nin GET params instead of POST-- now the activity accurately sets\nthe result. \nhttp://github.com/appcelerator/titanium_mobile/commit/f3bf194583833...
(from [39fb5c4c905df7e8d9b91b4d51be554d702b6671])\n[#1989 state:fixed-in-qa] Use the invocation\ncontext to determine which activity to pass to activitySupport, so\nwe can get results from activities. \nhttp://github.com/appcelerator/titanium_mobile/commit/39fb5c4c905df...
(from [d5d8dbe632f6fef21799b160f1c56359d89b751e])\n[#1989 state:fixed-in-qa] Put the cancel url back\nto fbconnect:cancel (instead of fbconnect://cancel), which matches\nFacebook's own setting per \nhttp://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac7...\n\nhttp://github.com/appcelerator/titanium_mobile/commit/d5d8dbe632f6f...
(from [7376f0231dd1383947abbf484a137316329bd4b5])\n[#1989 state:fixed-in-qa] Put the cancel url back\nto fbconnect:cancel (instead of fbconnect://cancel), which matches\nFacebook's own setting per \nhttp://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac7...\n\nhttp://github.com/appcelerator/titanium_mobile/commit/7376f0231dd13...
g1 running 1.6 and the sim running 2.2 Ti Mobile sdk\n1.5.0.02c264