1
Page Mounted and Focused Events trigger again after Initial View is Dismissed
complete
A
Awesomeosep
Hello,
About a month ago, we noticed that the page-mounted and focused events on several of our screens had begun triggering twice.
For more context, two issues were occurring. One was that the page-mounted and page-focused events would trigger twice when any page loaded on the web. The second issue was that the “Dismiss Initial View” function caused the Initial View page’s mounted event to trigger again. Also, these bugs only seemed to occur in apps with direct third-party auth enabled.
Issue #1 seems to have been resolved now, but issue #2 is still occurring. The “Dismiss initial view” function still causes the initial view’s (the auth page in our case) page-mounted and focused events to run a second time.
We managed to reproduce the issue in a new test app (with 3rd party auth enabled). The issue also occurs in web builds, and not just in the preview. (We haven’t tested on mobile, so we don’t know if it occurs there too.)
Initially, we figured out that this was causing an increase in our Firestore reads (and costs), but as Issue #1 is now resolved, this is less of a problem and we are writing this post simply to notify the Appgyver team of this issue.
Thanks,
Awesomeosep
Log In
Activity
Newest
Oldest
T
Timo Kapanen
complete
T
Timo Kapanen
Hi Awesomeosep, do you have any further information regarding to this? See also Kristian's question. I am afraid that we would otherwise need to close this ticket as it is not actionable and see if we face this again at some point. Best Regards, Timo Kapanen
Kristian Gerkman
under review
Kristian Gerkman
Hey Awesomeosep, thanks for the report!
I tried to repro the second issue, but couldn't.. Do you have an app that does this always? I'd like to take a look at how it's done.
Thanks,
Kristian
T
Timo Kapanen
Awesomeosep, after awhile coming back to this. Could you check Kristian's question as currently this is unfortunately not actionable. Best Regards, Timo Kapanen
A
Awesomeosep
Timo Kapanen: Sorry for not responding... I don't think this issue is still present so you can go ahead and close the topic...
T
Timo Kapanen
Awesomeosep: very good, thanks for confirming