[TIMOB-2200] Android - facebook log in failure
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:58:23.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 M02 |
Components | Android |
Labels | android, defect, facebook |
Reporter | Thomas Huelbert |
Assignee | Marshall Culpepper |
Created | 2011-04-15T03:13:19.000+0000 |
Updated | 2011-04-17T01:58:23.000+0000 |
Description
This occurs in todays pull and in 1.4.1.1. In 1.6 and 2.2.
1.KS>Mashups>Facebook
2.Log in test, tap log in button
results: a blank page appears, output is:
D/KrollContext( 1287): (kroll$7) [716,9981877] Running evaluated
script: app://examples/facebook_login_logout.js
D/FBSession( 1287): FBUserId = 0
D/TiFacebook( 1287): (main) [1293,9983170] EXECUTE LOGIN CALLED
I/ActivityManager( 76): Starting activity: Intent {
act=login_dialog
cmp=com.appcelerator.KitchenSink/ti.modules.titanium.facebook.FBActivity
(has extras) }
I/ActivityManager( 76): Process com.android.calendar (pid 1406) has
died.
D/FBDialog( 1287): FBDialog onStart
D/FBDialog( 1287): FBDialog onResume
E/TiUIView( 1287): (main) [2040,9985210] TAP, TAP, TAP on
[Ti.Facebook.LoginButton]
D/dalvikvm( 1287): GC freed 7462 objects / 711784 bytes in
197ms
I/ActivityManager( 76): Displayed activity
com.appcelerator.KitchenSink/ti.modules.titanium.facebook.FBActivity:
2725 ms (total 2725 ms)
(from [d965244922008868150c1020306995ec558862cd]) [#2200] First push of using oauth in 1_4_X facebook module. Can be disabled by passing oauth:false as creation arg in createLoginButton(), but at the moment the old, non-oauth way is not working. http://github.com/appcelerator/titanium_mobile/commit/d965244922008868150c1020306995ec558862cd"> http://github.com/appcelerator/titanium_mobile/commit/d965244922008...
Standardizing the title and putting ticket into open state since it's being actively worked.
(from [2a27cc83c8f8f63a1a2ac68d600c0b489129a530]) [#2200] Facilitate adding FB permissions via the new oauth mechanism. http://github.com/appcelerator/titanium_mobile/commit/2a27cc83c8f8f63a1a2ac68d600c0b489129a530"> http://github.com/appcelerator/titanium_mobile/commit/2a27cc83c8f8f...
(from [3a7d5140b26a538e1852a56148ac3aa27599bcfc]) [#2200 state:fixed-in-qa] Round out the grafting of OAUTH login/authorizations on old API. https://github.com/appcelerator/titanium_mobile/commit/3a7d5140b26a538e1852a56148ac3aa27599bcfc"> https://github.com/appcelerator/titanium_mobile/commit/3a7d5140b26a...
reopening because i need to cherrypick to 1.5
Login & authorization fixed now in 1.5 as well.
(from [09a41c5b8215369533adbc33ec2f18f3d7808429]) [#2200] First push of using oauth in 1_4_X facebook module. Can be disabled by passing oauth:false as creation arg in createLoginButton(), but at the moment the old, non-oauth way is not working. https://github.com/appcelerator/titanium_mobile/commit/09a41c5b8215369533adbc33ec2f18f3d7808429"> https://github.com/appcelerator/titanium_mobile/commit/09a41c5b8215...
(from [f6caabb6fa7a6dbeafece870ffd4dc35aeeff56e]) [#2200 state:fixed-in-qa] Round out the grafting of OAUTH login/authorizations on old API.
fixed Conflicts:
https://github.com/appcelerator/titanium_mobile/commit/f6caabb6fa7a6dbeafece870ffd4dc35aeeff56e"> https://github.com/appcelerator/titanium_mobile/commit/f6caabb6fa7a...
(from [e2b8d5c62d7dbde94fa35698aaac830f23164f43]) [#2200] Facilitate adding FB permissions via the new oauth mechanism. https://github.com/appcelerator/titanium_mobile/commit/e2b8d5c62d7dbde94fa35698aaac830f23164f43"> https://github.com/appcelerator/titanium_mobile/commit/e2b8d5c62d7d...
hi Bill
what can we do in 1.4.1 to workaround this issue ?
This behavior persists in 1.5.0.fb4b340. G2 (2.2) 2.1 emulator
It was intended for 1.5 (I should've changed the milestone back then) because we planned to adopt the whole new Facebook SDK by then. It was only a 1_4_X fix for people who wanted to build it.
But in fact we dropped the new Facebook SDK from 1.5 milestones, so indeed we WILL need to do at least this OAUTH support for 1.5. Crap! :)
I'll cherry-pick the commits over.
Gosh, I must be confused. I already cherry-picked this to 1.5 on 11/3/10. @Thomas, I have no trouble running this in 1.5. Did it just now with my 2.2 device and 2.1 emulator.
I used build 069c20a (very recent) because I couldn't even get KS to launch with the build you mentioned.
closing against 1.5.0.91838a G2 (2.2), Droid 1 (2.2)