Resetting stopped timer triggers "On Timer End" events

[albluwi1987]

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

Hi,
In my app (Home Page) there is a Timer Widget and I've added (On Page Load Action) which is ((Starting that Timer widget)) and On Timer Widget "On Timer End Action" I've put 2 actions first to reset the timer and second to start the timer again AND the issue is after the timer end its Freezes/Broken the app and I can't Scroll in it or click on any buttons and to make it work again I have to close the app and open it again

Note: I've tested the app on run mode also on real device (TestFlight)
Any Help will be appreciated, Thanks

Expected Behavior

It supposed to work properly and start the timer again without any issues

Steps to Reproduce

1. Create new page
2. Add Timer Widget
3. Add action in (On Page Load) that start the Timer widget
4. On Timer widget Add 2 Actions in (On Timer End) first: Reset Timer, second: Start Timer
5. Run the App

Reproducible from Blank

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

Bug Report Code (Required)

IT4oz/Hqx89grs9J1s/IdfoxnSQWQkx/bbsrm8pOFC0YGOvyPbJ/duD7dhFtXemoY0NhHGGWpE8G7sGMiuHXG8E4GzeVc7V8+c1cFDvjRXq8RZiNDKudPXZ9P+VRG3Km15m3qxFSVeptWkIFwFzzPemtbAXtJ5+/Zwh9f6PHaOI=

Context

Its a Critical Bug for me because in my app many features needs Timer to work properly and Now I've stopped my app publishing until this issue fixed

Visual documentation

Already Uploaded in (Current Behavior) section

Additional Info

No response

Environment

- FlutterFlow version: v3.1 (released August 3, 2023)
- Platform: web
- Browser name and version: Chrome 115.0.5790.114
- Operating system and version affected: macOS Ventura 13.4.1 (c)

[kevintonb]

Hey @albluwi1987 , thank you for reporting this issue. I was able to reproduce the bug following the steps listed above.

[aemelyanovff]

This seems to be a bug in a pub.dev package that we use, stop_watch_timer. I created a pull request there: hukusuke1007/stop_watch_timer#37

[aemelyanovff]

Fixed in the next update!