The bug is in the compatibility library, not the platform, so no firmware
updates are involved.
The native platform implementation of this is different.
It appears fixed in the current version of the compat library (v7?), I
believe it has been for a long time.
-- K
26 апреля 2012 г. 6:32
Ok, I'll verify I have the current version of the compatibility library. If
it is fixed, what would cause my fragment's onActivityResult callback
method to never be called?
On Thursday, April 26, 2012 4:42:41 AM UTC-5, Kostya Vasilyev wrote:
The bug is in the compatibility library, not the
OK! I solved my problem. Teaches me to code when tired. I was simply
missing a .show() after my toast. :(
On Thursday, April 26, 2012 6:21:03 PM UTC-5, Casvah wrote:
Ok, I'll verify I have the current version of the compatibility library.
If it is fixed, what would cause my fragment's
Has this issue been fixed? The bug report on the issue tracker says it's
closed, but there are new comments from people having this issue. I am also
having this issue. I might be doing it wrong though, since I can't get it
to work with any request code.
On Thursday, March 10, 2011 12:15:12 PM
I am sure it will be fixed in whatever the next version of Android is and
if they back port the fix and the phones get updated (likelihood: 0.0001%).
So unless you are targeting ONLY the non-yet public next version of the
SDK, you might as well just not even assume this fix exists and code
Oh, I see this is from 2011, not this March. Never mind -- the fix should
certainly be part of 3.2 and ICS.
On Thursday, April 26, 2012 10:09:38 AM UTC+8, Zsolt Vasvari wrote:
I am sure it will be fixed in whatever the next version of Android is and
if they back port the fix and the phones
Ran into this issue tonight on my Droid (2.2). I think there's an issue in
FragmentActivity.startActivityFromFragment(...).
YMMV, but this seems to fix it for me:
https://github.com/petedoyle/android-support-v4-googlemaps/commit/06307de35a9de0a89ff52bb42a358ba6740e542c
Basically there are two
Whoops, yeah that is a bug. Thanks for finding it. I'll fix it in the next
update.
On Thu, Mar 10, 2011 at 1:55 AM, Pete Doyle petedo...@gmail.com wrote:
Ran into this issue tonight on my Droid (2.2). I think there's an issue in
FragmentActivity.startActivityFromFragment(...).
YMMV, but
I have an application that targets 2.1. I'm using the Android
Compatibility Package to migrate the code in my Activities to
Fragments. I had an Activity which was launching a contact picker as
follows:
Intent contactPickerIntent = new Intent(Intent.ACTION_PICK,
Contacts.CONTENT_URI);
Does the API demo for this work wherever you are running it? I have tested
it on 3.0, 2.3, and 1.6, and it works in those places, not would I expect it
to have any trouble elsewhere. (How this works is very simple, it just
masks out the top X bits of the request code to determine which fragment
10 matches
Mail list logo
