2 Replies
      Latest reply on Sep 9, 2019 5:51 AM by repgokjfhdg
      jbailey Level 1 Level 1 (0 points)

        Is anyone else having issues with becomeCurrentPage()? I've reported the issue with Feedback Assistant, but I'm looking for a workaround.

         

        I have a Page Based Navigation interface with 3 pages (Custom Controller, Customer Controller, Now Playing Controller). The first page has buttons to control the workout (like the apple workout app). The second page is the state of the current workout. When a button is pressed on the first page (pause/resume/cancel), a notification is sent to the second page. The second page calls the becomeCurrentPage() method. This has always worked, but in watchOS 6 the willActivate() method on the second page is called, but the didAppear() method is not called. The second page is showing, but the page dots is still on the first page.