Merge pull request #10523 from karahanharunn/known_issue_mobile_navigation

update docs for known issue in mobile

Author: MarkvanMents

content/en/docs/refguide/mobile/designing-mobile-user-interfaces/navigation.md

@@ -122,7 +122,7 @@ You can configure this behavior either on Close page actions that you have model
 
 The **All** option can be used to close all pages in the current stack.
 
-#### Combining Closing and Opening Pages
+#### Combining Closing and Opening Pages {#combining-closing-and-opening-pages}
 
 For more complex scenarios, it is possible to transparently remove one or more pages from the history from the current stack when navigating to a new page. Doing so ensures that users cannot inadvertently navigate back to pages that are no longer relevant. For example, when a user reaches the end of a three-step wizard flow, you can configure the Open page activity to open the third page and close the previous two pages at the same time. As a result, the user will see a single transition, and navigating back will not lead them to the first two pages.
 

content/en/docs/releasenotes/studio-pro/11/11.6.md

@@ -97,4 +97,8 @@ Additionally, page parameters can now be marked as **Optional** and be given a *
 - We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption.
 - We added a consistency check for code actions that have a filename that does not match the casing of the document name, which could cause issues on certain operating systems, and when deploying to the cloud environment.
 
+### Known Issues
 
+#### Mobile
+
+* When you [clear history](/refguide/mobile/designing-mobile-user-interfaces/navigation/#combining-closing-and-opening-pages) when navigating from a page without a bottom bar to a page with a bottom bar, the bottom bar does not display. We are aware of this issue and are working on a fix.