Problem with NoActionBar bar activity

[sdevpura5]

Hi, I tried to use this in my new app and it's working fine but when I used this with a no NoActionBar activity it's not showing properly on Flashbar.Gravity.TOP

This is my code which I am writing

Flashbar.Builder builder = new Flashbar.Builder(activity) .gravity(gravity) .title(title) .message(body) .enableSwipeToDismiss() .backgroundColorRes(R.color.colorPrimarylight) .enterAnimation(FlashAnim.with(activity) .animateBar() .duration(Flashbar.DURATION_SHORT) .alpha() .overshoot()); _flashBar=builder.build();

This is the preview of the problem

What should I do ?

[itishrishikesh]

I have the same problem

[guilhermeestevao]

Me too @itishrishikesh

[Slake07]

I am facing same problem.

[klevisndoka]

Me 2

[elek90]

This is fixed in 1.0.3

[ArLabDev]

Sorry, what is the expected behavior?
I'm testing the 1.0.3 both with ActionBar or NoActionBar theme (using then a Support ActionBar), the Flashbar appears over the ActionBar. Is it correct?
Is there a way to place it under the ActionBar like Material Design banners?https://material.io/design/components/banners.html

Thanks

[dhaivat77]

I am using the latest version 1.0.3

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
window.setFlags(WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS,
WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS)
}

If I am using in full screen with no limits layout. Flashbar is hiding behind the status bar.

And applying the theme "Theme.AppCompat.Light.NoActionBar"

[findyourexit]

I'm experience the same behaviour where the Flashbar instance appears behind the status bar. I'm using the AppCompat.NoActionBar theme and have tried everything that I can think of to have the Flashbar render below the status bar, rather than beneath it. No luck so far! (Using Flashbar 1.0.3)

[kazaky]

me too having the same prob!

[swetanandha]

This is fixed in 1.0.3

not working

[lastpeony]

same problem

[LuiguiBalarezo]

same problem

[rolama]

same problem

[bybozyurt]

I had the same problem, it was fixed when I started using version 1.0.3