Fixed
Status Update
Comments
ni...@gmail.com <ni...@gmail.com> #2
I am getting the same problem after the latest update...
al...@android.com <al...@android.com>
bo...@gmail.com <bo...@gmail.com> #3
I think this might be the same as issue 36949180 . As mentioned in the comments there, try:
As a temporary workaround, try turning off Preferences > Compiler > Use External Build.
As a temporary workaround, try turning off Preferences > Compiler > Use External Build.
cr...@gmail.com <cr...@gmail.com> #4
Deleting the out folder before rebuilding solves the problem
al...@android.com <al...@android.com> #5
turning off Preferences > Compiler > Use External Build doesn't work if you have other modules as dependencies.
ni...@gmail.com <ni...@gmail.com> #6
I'm having the same problem.
[Deleted User] <[Deleted User]> #8
Also having this problem, but turning off Preferences > Compiler > Use External Build worked for me, even though I have other modules as dependencies, despite what jai.chan mentioned.
ni...@gmail.com <ni...@gmail.com> #9
[Comment deleted]
ni...@gmail.com <ni...@gmail.com> #10
Problem exists. Turning off "Use external build" helps.
au...@google.com <au...@google.com> #11
Also having the same problem.But I don't know How can I fix ?
ni...@gmail.com <ni...@gmail.com> #12
The problem is still there... :s
[Deleted User] <[Deleted User]> #13
having the same issue here too
ak...@gmail.com <ak...@gmail.com> #14
Still happens
th...@gmail.com <th...@gmail.com> #15
A shame that google is not able to solve this issue since several years but is able to pop out yet another android version.
vn...@gmail.com <vn...@gmail.com> #16
Android Studio 1.4 and this or similar bug is still here! My project is completely blocked due to inability to add a new activity class without getting "cannot find symbol" for it. The other classes are getting compiled except that activty. I've checked in the build/intermediates/classes - the activity .class is missing, not even compiled though it is hollow class, no syntax error.
Already tried:
Invalidate Cache and Restart - nope
Deleted /build directory and rebuild - nope
./gradlew clean of entire project - nope
Restarting after everything above - nope
Recreating a new blank activity - nope
Checked manifest entries for the activity - nope
Combination of the above - nope
Desperation mode: on
Already tried:
Invalidate Cache and Restart - nope
Deleted /build directory and rebuild - nope
./gradlew clean of entire project - nope
Restarting after everything above - nope
Recreating a new blank activity - nope
Checked manifest entries for the activity - nope
Combination of the above - nope
Desperation mode: on
gd...@gmail.com <gd...@gmail.com> #17
I've just managed to workaround it! Simple Refactor > Move to another package did remove the error, but after I moved it back to the original package the error appeared again. Have NO idea what's going on!
sh...@gmail.com <sh...@gmail.com> #18
Damn, I've found that class in the long forgotten exclude list in my build.gradle! What a stupid mistake of mine. Mystery revealed! (chuckle)
au...@google.com <au...@google.com>
bo...@gmail.com <bo...@gmail.com> #19
The target release was 25.0.1 and we're now at 26.0.0-beta2. Could you guys at least put an actual, realistic target on this issue?
ga...@google.com <ga...@google.com> #20
Scrolling behavior with CoordinatorLayout has been implemented, and should be available in the next release.
Passing bug to Avigail to comment about bottom nav elevation behavior.
Passing bug to Avigail to comment about bottom nav elevation behavior.
ka...@gmail.com <ka...@gmail.com> #21
I could not find any info about this, is this released ?
cm...@gmail.com <cm...@gmail.com> #22
Any news on when this will be released?
bo...@gmail.com <bo...@gmail.com> #23
I'm revisiting a project with this issue and this is still not fixed on v27.1.1. If I have a BottomNavigationView inside a parent CoordinatorLayout, it doesn't scroll. It works though perfectly when manually setting translationY:
appBarLayout.addOnOffsetChangedListener(new AppBarLayout.OnOffsetChangedListener() {
@Override
public void onOffsetChanged(AppBarLayout appBarLayout, int verticalOffset) {
bottomNavigationView.setTranslationY(verticalOffset*-1);
}
});
However, when trying the same technique, while having the BottomNavigationView inside a FrameLayout, which itself is the child of the parent CoordinatorLayout, the BottomNavigationView doesn't even show up in the UI.
Trying the same AppBarLayout OffsetChangedListener on a different UI component (such as a FAB), while inside the FrameLayout, works just as if the FAB was a direct child of the CoordinatorLayout.
So what's the difference between the 2 setups? Why does the FAB work, but not the BottomNavigationView?
Also, where's the scrolling behavior that was about to be released?
appBarLayout.addOnOffsetChangedListener(new AppBarLayout.OnOffsetChangedListener() {
@Override
public void onOffsetChanged(AppBarLayout appBarLayout, int verticalOffset) {
bottomNavigationView.setTranslationY(verticalOffset*-1);
}
});
However, when trying the same technique, while having the BottomNavigationView inside a FrameLayout, which itself is the child of the parent CoordinatorLayout, the BottomNavigationView doesn't even show up in the UI.
Trying the same AppBarLayout OffsetChangedListener on a different UI component (such as a FAB), while inside the FrameLayout, works just as if the FAB was a direct child of the CoordinatorLayout.
So what's the difference between the 2 setups? Why does the FAB work, but not the BottomNavigationView?
Also, where's the scrolling behavior that was about to be released?
af...@google.com <af...@google.com> #24
Scrolling behavior has been added. You can use it by setting a HideBottomViewOnScrollBehavior on the BottomNavigationView: app:layout_behavior="@string/hide_bottom_view_on_scroll_behavior".
See class documentation for BottomNavigationView:https://developer.android.com/reference/com/google/android/material/bottomnavigation/BottomNavigationView .
And for HideBottomViewOnScrollBehavior:https://developer.android.com/reference/com/google/android/material/behavior/HideBottomViewOnScrollBehavior .
This is available in our 28.0.0-alpha1 release or the 1.0.0-alpha1 release or later.
See class documentation for BottomNavigationView:
And for HideBottomViewOnScrollBehavior:
This is available in our 28.0.0-alpha1 release or the 1.0.0-alpha1 release or later.
pu...@gmail.com <pu...@gmail.com> #25
When the bottom bar is partly visible (eg user scrolled just a bit and stopped scrolling), does the bottom bar snaps automatically to either be fully visible or hidden like
a CollapsingToolbarLayout would do with app:layout_scrollFlags="scroll|snap" ?
a CollapsingToolbarLayout would do with app:layout_scrollFlags="scroll|snap" ?
ga...@gmail.com <ga...@gmail.com> #26
Im on 28.0.0 and the bottom shadow still doesnt show up at the top when i set the app:elevation in BNV.
is it yet to be fixed ? Here is my layout
<android.support.design.widget.BottomNavigationView
android:id="@+id/landing_bottom_nav"
android:layout_width="0dp"
android:layout_height="wrap_content"
android:background="@color/white"
app:elevation="4dp"
android:elevation="4dp"
app:layout_constraintBottom_toBottomOf="parent"
app:menu="@menu/landing_menu"/>
is it yet to be fixed ? Here is my layout
<android.support.design.widget.BottomNavigationView
android:id="@+id/landing_bottom_nav"
android:layout_width="0dp"
android:layout_height="wrap_content"
android:background="@color/white"
app:elevation="4dp"
android:elevation="4dp"
app:layout_constraintBottom_toBottomOf="parent"
app:menu="@menu/landing_menu"/>
sr...@gmail.com <sr...@gmail.com> #27
With this HideBottomViewOnScrollBehavior , Scrolling behavior working fine but, Showing white space occupying the size of that bottom view.
af...@google.com <af...@google.com> #28
@srinivasmakkena058 Could you please provide a video showing the scrolling whitespace issue? And could you file a separate issue, since the scroll behavior doesn't appear to be missing, which is the issue described in the title of this bug?
@pujos.michael Please file a separate bug about elevation concerns. I looked into bottom navigation elevation a couple years back, and I believe it's actually sort of WAI that the shadow hardly shows -- the light source is at the top of the screen which would make the shadow show at the bottom of the bar. Happy to discuss and address in a separate issue, but let's keep this one focused on scroll behavior.
Description
Version used: 25.0.0
Theme used: Any
Devices/Android versions reproduced on: Any >= KitKat
BottomNavigationView is missing:
- Scrolling behavior inside CoordinatorLayout
- 8dp elevation in order to be above the snackbar.
Relevant link: