Console is throwing:
WARNING: This application uses deprecated jQuery 2.2 features. Please see the Javascript console for more details. Error: jQuery.fx.interval is deprecated
I believe it is related to the external library BeautifulSoup.
Thoughts?
Console is throwing:
WARNING: This application uses deprecated jQuery 2.2 features. Please see the Javascript console for more details. Error: jQuery.fx.interval is deprecated
I believe it is related to the external library BeautifulSoup.
Thoughts?
This definitely isn’t related to BeautifulSoup, which is only available on the server. Would you mind PM-ing me a clone link for your app so I can take a look?
Yesterday I saw the same message for a few minutes, then it disappeared. I am importing only datetime on the server side, nothing on the client side (other than the usual anvil libraries).
I am getting this error as well. Not everytime I run the app but periodically. I am wondering if jquery is somehow in the CRM template I started from.
I’m still trying to chase this one down. It happens very occasionally to me. In the meantime, I should reassure you that it definitely isn’t causing any issues, it’s just a warning!
I seem to get this if I have intermittent connectivity, on a train for instance…
Seem being the operative word - I don’t know if I’m imagining this link!
Thank-you! That gives us some hints as to where to look…
Sorry to ruin the lead, but I’ve received it several times today and I’m working on a wired home internet connection…
Today it has been appearing when I ‘Run’ the app from the IDE, and normally after I’ve changed something. It might be related to changes made to the form init method… but again potentially a red herring
I got this error again this morning, and it happened alongside making an anvil.server.call
Could be unrelated but the more datapoints the easier it’ll be to find!
@mattstibbs - Thank you! This stack trace was exactly what I needed, and which I hadn’t been able to capture myself.
I’m delighted to report that this is a bug in jQuery (or its migration library), which I have now reported. Once it’s fixed on there, I’ll be sure to merge the fix into Anvil. In the meantime, I have switched Anvil to a patched version of jQuery that doesn’t have the problem. This will go live in the next day or two.
Thanks for your help, everyone!
[UPDATE: This fix is now live]