search

JakeWharton / ActionBarSherlock

[DEPRECATED] Action bar implementation which uses the native action bar on Android 4.0+ and a custom implementation on pre-4.0 through a single API and theme.
http://actionbarsherlock.com
Apache License 2.0
7.1k stars 3.53k forks source link

Disappearing ActionBar after finishing ActionMode #1014

Open KamilLelonek opened 11 years ago

KamilLelonek commented 11 years ago

I've implemented ActionMode with SherlockActionBar and everything works fine, but only on devices post HONEYCOMB.

On older APIs I have the following problem:

Everything is fine when I start my app:

enter image description here

All goes well even when I start action mode and select a couple of items:

enter image description here

But when I exit (finish) action mode ActionBarSherlock crashes. I mean that it's no loger visible, only when I start or finish action mode, it blinks very shortly that I can see icons: enter image description here

So only updates show ActionBar for a short moment (it blinks), but after that it remains "hidden" (covered) again.

Has anyone similar problem? Is there any sollution for that?

KamilLelonek commented 11 years ago

Preview

bradmcmanus commented 11 years ago

I am seeing the same exact behavior. Are you using ABS 4.3? I am investigating it now. I'm going to try updating to latest, too.

KamilLelonek commented 11 years ago

Yes, I've tested it with both 4.2 and 4.3.

rishabhmhjn commented 11 years ago

I had the same problem in an Android version 4.3 device

bradmcmanus commented 11 years ago

Ah, strange. I only see the unwanted behavior on a device running Gingerbread. I suspected it was a problem with the ported ActionMode and other ActionBar related classes necessary for 2.3 devices.

rishabhmhjn commented 11 years ago

My problem is when I scroll through a list in the activity, the actionbar disappears and come backs upon touching at its position. I do not use action mode though.

KamilLelonek commented 11 years ago

Are u using some custom list view or something or everything goes the "normal way"?

bradmcmanus commented 11 years ago

Seems to be a problem either way. In one case the ActionBar is using a customView, in another case the ActionBar just has an icon and title set on it.

bradmcmanus commented 11 years ago

FYI, we tracked it down to being an issue with NOA. We removed the ABS included NOA in favor of the NOA jar, and this was the source of the contextual action bar issue.

KamilLelonek commented 11 years ago

What does NOA stand for? Is the problem solved?

bradmcmanus commented 11 years ago

Ah, NineOldAndroids. ABS includes a stripped down version of NineOldAndroids in its source but there is also a standalone NineOldAndroids library with more features. Our problem was resolved by making sure to use the com.actionbarsherlock.internal.nineoldandroids (as happens by default, unless you modify the ABS source).

KamilLelonek commented 11 years ago

I use modified ABS without NOA package, which is provided from external library project, because previous configuration (NOA package and NOA library which is required by project) caused conflicts.

jenzz commented 10 years ago

Yep. I can confirm using the com.actionbarsherlock.internal.nineoldandroids methods instead of an external .jar fixes this issue.