La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
Hello community, I've facing this issue on my nextjs app and it's causing my app to break when this console error pops up. Any help available?
leadflows.js:1 Uncaught TypeError: t.report is not a function at Object.getPortalId (leadflows.js:1) at Object.setUpErrorReporting (leadflows.js:11) at Object.setUp (leadflows.js:11) at a (leadflows.js:11) at leadflows.js:11 at leadflows.js:11
Any update to this issue? I'm encountering the same problem. Building a Next.js Project that utilizes Hubspot forms. Doesn't seem to be much information out there besides this single thread. Any advice would be appreciated.
We are having a similiar issue with our Nextjs project. I keep getting "Cannot read property reportCount of undefined" bugs which cause an error overlay to appear. This causes local development to be very annoying. Any tips on how to prevent that error from occuring would be great
oct. 29, 20205:34 PM - modifié oct. 30, 20201:57 AM
Membre
LeadFlow Errors
Yes! I do get these errors after I successfully subscribe as a lead.
At first, I suspected the inclusion of reCAPTCHA on the contact form so I took it off but there was no luck. Currently I'm including the tracking code as a header script tag in nextjs and maybe that could also be the issue but I'm not too sure as it works very fine until I ( or any user) subscribes via the contact form then the issues starts occuring.
In conclusion, I would like to know if there's an alternative solution of implementing hubspot integration in a webapp apart from using the script tag. Thank you.
@dennisedson@Malvin_j that's a new one for me. But, I also don't have much nextjs experience. I wonder if it's trying to codesplit the 3rd party hubspot script?