Fixed
Status Update
No update yet.
Comments
ap...@google.com
I created a thread on the android-developers forum related to this bug:
http://groups.google.com/group/android-
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
ap...@google.com
My personal theory is that Google broke this part of the API intentionally to keep
the lock-in on sync functionality they've enjoyed since Android 1.0.....
the lock-in on sync functionality they've enjoyed since Android 1.0.....
Description
The new ActivityResult APIs have been released, and the old APIs in FragmentActivity and FragmentHostCallback have been deprecated.
We should re-implement the old Fragment Activity Result APIs (startActivityForResult, StartIntentSenderForResult, and RequestPermissions) in terms of the new APIs.