Weirdly enough, it works for both of us when we use Google Chrome though.
I'm wondering, how can I reproduce the issue in our browsers to uncover why this is happening? Is there any way to export environmental variables that ReTool is using, or capture the browser state beyond this console.log? I'd like to get this public app working for all browsers that are customers may be using. Thank you!
I just asked my staff to record a Loom, and it looks like another member is experiencing the same issue (of, can't find variable a), and then causing a 404.
Thank you for reporting this issue. I haven't been able to reproduce yet. Is this a shortened loop of the loom your staff recorded? If so, would you mind dropping the loom link?
One more thing we can try is upgrading to a newer version of Safari Retool supports, version 17.5. Another thing that may be helpful is looking into what extensions these users have or settings they have enabled to see if that could be the cause.
Got it. It sounds like this is mostly a niche issue for that user, so we won’t worry about it for now. If it comes up en masse, we’ll investigate further!