I’m another happy BDK native customer and @gaurav 's fan.
There is one thing that I’m struggling with and that is the Android Back Button, so wondering how you folks handle it.
In my case - I use a combination of Bubble’s go to page and BDK’s Navigate to link options to take my user to a different page. The BDK’s navigate to link works as intended, but tends to be a lot slower than Bubble’s Go To page and hence my question on how the android back button works in this environment.
My workflow is as follows:
When ELEMENT A is clicked on Page A ----> Show Element B (a loader or a pop up that is not visible on page load) ------> Go to Page B.
Now when I press the android back button from Page B, it goes to Page A, but the Show Element (pop up or loader) is showing up.
Even if I do a ‘WHEN ANDROID BACK BUTTON IS PRESSED’, go to page A, in the workflow, it goes to Page A and the pop up is still showing. It kind of seems to ‘remember’ the flow before it actually went to Page B.
I’ve even tried 'WHEN PAGE LOADED and ELEMENT (pop up or loader) is visible, hide element. Doesn’t seem to work.
Would be obliged to have any help in this case. Or should I bite the bullet and add the Navigate to link (with condition of for native app), in all my workflows that involve going to a different page. I have 350 of them.
Thank you in advance for your help.