Bug: no back button on Golden Ticket


(Bob) #1

iPhone 6 Plus, iOS 10.3.2

When tapping on notification to view a new golden ticket, around 50% of the time there’s no back button to come out of the view. I have to double-click the home button and close the app from the app switcher screen to get out of this screen:

…and here with the back button top left of screen:


Flux: The End of Paper Receipts & Loyalty Cards
Give/Request Golden Tickets 🎫 / Jump The Queue
#2

Hey Bob,

Thanks a lot for reporting this :bug:. I’ll investigate and flag it to our iOS engineers! :crossed_fingers: By the way, you mentioned that you have to close the app to get back out of this screen. If you just tap home and open the app again it’s still no game?

Priscila


(Bob) #4

@priscila, I closed the app as suggested, opened the app and I’m presented with the same screen, no back button. Hope that helps!


#5

Thank you for checking @BobT! We’re onto it! :microscope:


(Bob) #6

Just to confirm, this occurs intermittently when opening a golden ticket notification, not the in-app feed which seems to be fine.

You should easily be able to test this by continuing to award yourself a golden ticket and opening it from the pop-up notification… not that I’m trying to teach you to suck eggs, just trying to describe the issue as best as I can :joy:


(Rika Raybould) #7

I’ve just tracked down a 100% reproducible test case for the iOS team. It required a bit of support access since it’s caused by something we do from our interface. :smile:

Thanks so much for the report! :heart:


#8

Looks like I’ve just had the same issue with a Flux notification

https://community.monzo.com/t/flux-the-end-of-paper-receipts-loyalty-cards/7951/132?u=haitch


#9

And another one where I’ve clicked on a notification from Flux and there’s no back button.

Is anyone from Monzo still looking at these @RichardR?


Known issues / bugs 🐛🐜🐞
(Rika Raybould) #10

I’ll add this to the ongoing ticket. This screen works a little differently to the golden ticket one but should be the same issue to fix here too. :+1: