[TIMOB-1989] Android: Callbacks for Facebook publishStream never occur
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:57:45.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 |
| Components | Android |
| Labels | android, defect, facebook, rplist |
| Reporter | Bill Dawson |
| Assignee | Bill Dawson |
| Created | 2011-04-15T03:07:28.000+0000 |
| Updated | 2011-04-17T01:57:45.000+0000 |
Description
Fail case is to be seen also in our KitchenSink. Go to Mashups - Facebook - Publish Stream (or Publish Status). Do a Facebook status update and you should get an alert dialog after you are finished, but you don't. The facebook update occurs as planned, but the alert -- which should tell you "Your status was published" -- is generated from inside the callback function, which never fires.
(from [671ca48045584277d384bd5f3203ca9b40e73848]) [#1989] Check for requestCode instead of resultCode when finding callbacks. Now callbacks occur, but the problem is the result code is always 0 which sets success to false. http://github.com/appcelerator/titanium_mobile/commit/671ca48045584277d384bd5f3203ca9b40e73848"> http://github.com/appcelerator/titanium_mobile/commit/671ca48045584...
So i got the callback to fire, but it always thinks that
successisfalse.(from [caff4cd3e2c8a70e76d6b9c8a3c67f39ac2af888]) [#1989] Recent change to compiler.py made activity and permission detection fail. After discussing with marshall, taking out that change so Facebook activity gets put successfully into AndroidManifest. http://github.com/appcelerator/titanium_mobile/commit/caff4cd3e2c8a70e76d6b9c8a3c67f39ac2af888"> http://github.com/appcelerator/titanium_mobile/commit/caff4cd3e2c8a...
(from [4b3b3d5e03e98363198532c0d62e52568f024476]) [#1989] Put the facebook success/cancel urls in GET params instead of POST-- now the activity accurately sets the result. http://github.com/appcelerator/titanium_mobile/commit/4b3b3d5e03e98363198532c0d62e52568f024476"> http://github.com/appcelerator/titanium_mobile/commit/4b3b3d5e03e98...
(from [f3bf1945838339091296179fd2179913d11165c3]) [#1989] Put the facebook success/cancel urls in GET params instead of POST-- now the activity accurately sets the result. http://github.com/appcelerator/titanium_mobile/commit/f3bf1945838339091296179fd2179913d11165c3"> http://github.com/appcelerator/titanium_mobile/commit/f3bf194583833...
(from [39fb5c4c905df7e8d9b91b4d51be554d702b6671]) [#1989 state:fixed-in-qa] Use the invocation context to determine which activity to pass to activitySupport, so we can get results from activities. http://github.com/appcelerator/titanium_mobile/commit/39fb5c4c905df7e8d9b91b4d51be554d702b6671"> http://github.com/appcelerator/titanium_mobile/commit/39fb5c4c905df...
(from [d5d8dbe632f6fef21799b160f1c56359d89b751e]) [#1989 state:fixed-in-qa] Put the cancel url back to fbconnect:cancel (instead of fbconnect://cancel), which matches Facebook's own setting per http://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac75cda7b6787a7fcb6f4bcd35b7b/facebook/src/com/facebook/android/Facebook.java#L42"> http://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac7... http://github.com/appcelerator/titanium_mobile/commit/d5d8dbe632f6fef21799b160f1c56359d89b751e"> http://github.com/appcelerator/titanium_mobile/commit/d5d8dbe632f6f...
(from [7376f0231dd1383947abbf484a137316329bd4b5]) [#1989 state:fixed-in-qa] Put the cancel url back to fbconnect:cancel (instead of fbconnect://cancel), which matches Facebook's own setting per http://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac75cda7b6787a7fcb6f4bcd35b7b/facebook/src/com/facebook/android/Facebook.java#L42"> http://github.com/facebook/facebook-android-sdk/blob/ef53183c59dac7... http://github.com/appcelerator/titanium_mobile/commit/7376f0231dd1383947abbf484a137316329bd4b5"> http://github.com/appcelerator/titanium_mobile/commit/7376f0231dd13...
g1 running 1.6 and the sim running 2.2 Ti Mobile sdk 1.5.0.02c264