Yeah… I was also amazed by seeing the Screen [dot] back_pressed block…
I was like : it’s not in the release notes! when did it come?!
I think, back buttons on android are not working bcoz of this only. coz it’s a new block - we haven’t added anything to trigger when back is pressed… that’s why Thunkable is not letting us press back.
/ it’s my own dumb thought.
Hope seeing the App [dot] exit block soon!
Thanks!
Can someone describe in a little more detail what the issue is with the back button now? Is there something that used to work differently than it used to? If so, what exactly is it?
Around a month ago, when I was uploading v6 of my app, which is only for Android, till v5 everything was fast. after v6, the ap started hanging. each button took 6 seconds to respond, everyone needed to click the text_input 6-7 times for entering anything; the navigation became slow between.
I thought, “ok. this happens with every app sometimes” & ignored it.
I went till v9, then suddenly on every android device, the device’s default back button stopped working. even clicking tons of times, waiting as long as a minute for it should respond something…
I need to switch to stack_navigator because it has it’s own top-mounted back button.
Is it a bug? or something?
Thank you for pointing out the issue. Can you please share more information about this block? The location and a screenshot may be helpful for us to find out the issue on our side.