Fragment Backport requires seperate class for the backport and for the honeycomb?

Question

Am I missing something important in this, or do you have to maintain a seperate version of all your fragments for the backported classes, and for the native honeycomb fragments?

-- Attempting to use the backported fragments on honeycomb was expected to do a fall-through and use the native, not crash because of a ClassCastException

Any help would be greatly appreciated.

Answer 1

Oh my, well don't I feel silly.

Found the problem -- I was running a preview version of the emulator, I never remembered to delete it and replace it with a level 11 instance -- works fine in the final Honeycomb emulator.