Use separate container for ContactsUnavailableFragment
Having 2 fragments in the same container view was causing issues
with the fragment back stack on older API levels when navigating in
suggestions screen.
Test
manually verified that navigation works as expected when the contacts
list is empty on API 22 and 23 emulators
Bug 32621879
Change-Id: I77d5accd822edfcf5ef1c3a50c0e3d3cdbe508ae
diff --git a/res/layout/people_activity.xml b/res/layout/people_activity.xml
index 8810af0..978f47a 100644
--- a/res/layout/people_activity.xml
+++ b/res/layout/people_activity.xml
@@ -20,6 +20,14 @@
android:layout_width="match_parent"
android:layout_height="match_parent" >
+ <!-- This is kind of a hack. Really we should be able to put the ContactsUnavailableFragment
+ into contacts_list_container but that causes issues with the fragment back stack
+ on older API levels -->
+ <FrameLayout
+ android:id="@+id/contacts_unavailable_container"
+ android:layout_height="match_parent"
+ android:layout_width="match_parent" />
+
<FrameLayout
android:id="@+id/contacts_list_container"
android:layout_height="match_parent"