Thank you so much Evgene. Sorry, but I don't see any attachment to either this post or the associated email.
Thank you so much Evgene. Sorry, but I don't see any attachment to either this post or the associated email.
Evgene, what debugger and browser are you using to show these errors - the default debugger of some desktop browser? Weinre on the iPhone along with some desktop browser? Did they appear only after the sixth step of the procedure to duplicate the hanging on the iPhone?
Hi Robert,
We have tested your application on desktop Chrome browser using Chrome Developer Tools (F12). These errors appeared after the fourth step (hit the "+" icon in the header).
UPDATE: Bug found... thank you support for all your help. The problem was a line of code...
t8 = Number.parseFloat(t50);
... caused by either t50 already being a numeric 1 coming from local storage, or t8 not having been declared earlier.
Although frustrating, it was a good learning experience. The most important lessen for me (not being a strong debug tool user) is the usefulness of simply triangulating with Alerts to hone in on offending lines when the problem is on a device but not the desktop. I'm sure this is not the preferred approach, but it worked beautifully for me.
Again, my sincere thanks to Appery support for their assistance. It's genuinely appreciated.
Hi Robert,
Thank you for the feedback! Glad it's working.