This looks eerily similar to Bug #497 - except it seems to start happening AFTER a tree was already successfully entered AND the screen was cleared at least once. This is being seen on the current release (build 81, 4.1.4).
I've Repo'd this bug BOTH when USING TreeBot and WHEN NOT USING TreeBot.
Like mentioned above - it happens on the 2nd time a user is making an entry.
These videos were all taken on ios devices. Notably the tree - even though the screen DOES NOT clear and the 'Success!' msg box DOES NOT appear - the tree IS saved to the backend.
ToDO:
This looks eerily similar to Bug #497 - except it seems to start happening AFTER a tree was already successfully entered AND the screen was cleared at least once. This is being seen on the current release (build 81, 4.1.4).
I've Repo'd this bug BOTH when USING TreeBot and WHEN NOT USING TreeBot.
Like mentioned above - it happens on the 2nd time a user is making an entry.
These videos were all taken on ios devices. Notably the tree - even though the screen DOES NOT clear and the 'Success!' msg box DOES NOT appear - the tree IS saved to the backend.
Video 1 (error AFTER a tree has been entered):
https://github.com/TreeMama/iSeaTree-React-Prototype/assets/62637055/43b41182-9eaf-49e2-a727-a98efb5370fb
Video 2 (full workflow showing error - 1st a successful tree is entered THEN the error appears entering the 2nd tree immediately afterwards):
https://github.com/TreeMama/iSeaTree-React-Prototype/assets/62637055/41930baa-fb82-4c50-8bec-8e753a679202