Button state inquiry

add the page refresh tag to the screen, so when you «goback» it is reset. Give it a try and let me know. Good luck, Nour

@Nour Elhattab It works when the tag is [refresh:pull], and i pull down the screen cause everything refreshes as result but when it’s [refresh:always], the buttons still do the same thing

Can you share a file example @Andrew Ogwang? or did you solve it?

@Karla Fernandes | design & no-code I haven’t exactly solved it but i got a work around. Had to change what the pressesd button looks like so that even when it appears on top of the default it can’t be noticed. File example of what exactly though. The figma designs?

I noticed that there might be other apps facing this issue. I’ve looked at Tripmix and it seems to face a similar problem. Idk if the team that designed the app is aware though. Bravo Studio might have to look into this

@Andrew Ogwang yes, can I check the figma file example? or even your Bravo Vision app? :)

I got a solution to that problem that works for me. Maybe you could help me out with another. page tabs isn’t responding as it should. This is the link: https://www.figma.com/design/c4Cjv1wkpmaz7P7zyoYy7L/Profile?node-id=0-1&t=xy3DwrkCC00Ll8FI-1. On the bravo vision app, the part where the page tabs is supposed to appear, it’s just a blank space.

Hey Andrew, a few tips:

- put [skip] tag on all frames you aren't using yet
- in the component properties change the name of the property from “active” to "state“, active and default are the values of that property.

Watch video

Component states | Bravo Studio Help Center

I believe this is what is happening there ;-)

SM-A145P_20250716185339.mp4

This what I'm talking about. The pressed state remains when you go back to the page where the button was pressed.

I also wanted to inquire though. Does bravo studio support the firestore database because I keep getting 401 and 403 errors

@Andrew Ogwang yes, but you names the variable wrong. you need to use the right name for it to work.

And yes, you can create all kinds of screens for errors ;)

I’ll rename the variables. I’m aware that you can create screens for errors. My issue is that whenever I send a get request to the firestore api it brings errors regardless of following the documentation line for line. I even change my firestore database rules and it’s still the same result. So is it possible to use the firestore database as my app database

@Karla Fernandes | design & no-code It’s okay I’m switching to Xano. Thanks for support