Timer no funciona cuando hay una conexion realizad en Backend Query

[desof]

Has your issue been reported?

• I have searched the existing issues and confirm it has not been reported.
• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

El timer es llamado (Start Timer) en el EVento de On Page Load y nunca enciende si esta asiganado un Backend Query

Expected Behavior

deberia encender

Steps to Reproduce

1- nueva pagina
2- agrega columna
3- contenedor dentro de Columna
4- timer dentro del Contenedor
5- Agregar Backend Query (Firestore) al Contenedor

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4wlfLqw89OxLlE7rrUd8JanjgXMjs5UI0ZkdVxTis8GZT0B4kcYs+kfklUOOG4dAk3eGCKmmcX/Mruk/HpLvI4PReVGKZN/5BbWw3wfECiMrKvCq63b3BRLJ5PChWb56Wo3RJ5LtJodC0R3DmqHeu/ThDfJOb6PjEvPOaoXdeK2SrDX1iXc2URm05KZDPz

Context

Simplemente que el timer funcione para realizar una accion

Visual documentation

Captura de pantalla 2023-12-22 181652.png

Additional Info

Windows 11
FF V4 - (3.13.7)
Brave 1.61.104

Environment

- FlutterFlow version: FF V4 - (3.13.7)
- Platform: WINDOWS
- Browser name and version: Brave 1.61.104
- Operating system and version affected: 11

[hariprasadms]

Hi @desof - Thank you for submitting the issue. Could you please update the contents of the issue to English language? This is to ensure that the issue details readable for everyone in general. Appreciate your cooperation.

[hariprasadms]

I can confirm that I can reproduce the issue. Thanks

[sync-by-unito]

➤ Hariprasad commented:

Dev note - Below is the video showing the timer configuration when page got fire-store query associated.

I also noticed two points below,

1. Timer value defined in page state is not consider in the countdown time.
2. When countdown time value is set from a variable, UI not showing the variable binding instead it shows the default value from the countdown time field.

[Nic61]

I also encouter the same bug if I place an API call and right after the 'start timer' action. It's still a 'on page load' event.