Patrick@FullStory

Hi @arriye would you please provide the error output about the ReferenceError and when the error is thrown (i.e. during the build or at run time)

Hi @gaelbonjour thanks for reaching out to us. If an ad blocker blocks `fs.js`, you should still be able to call API functions from the SDK without throwing errors as...

Hi @acomito thanks for using our browser SDK! I looked into this and was able to reproduce by adding a `'` character to the end of my `orgId` parameter like...

Hey @amcdnl thanks for the feedback! We've been discussing adding some kind of lifecycle event concept to the recording process. would something like ``` FullStory.ready(({ sessionUrl }) => { operation.setContext(({...

> Though I would NOT prefer that in this case since hook is used on every API request thus the handlers would be annoying - here i would prefer a...

Hey @amcdnl There is a way to get the check you want, but it isn't explicit in the API. If FullStory isn't ready, then `FullStory.getCurrentSessionURL(true)` (or `FullStory.getCurrentSessionURL()`) will return `null`...

> Last time I tried this it threw an error. In the non-npm FullStory library (i.e. the snippet tag), `getCurrentSessionURL` isn't defined until the FullStory recorder is fully bootstrapped, so...

Hey @id0Sch thanks for your suggestion! We'll look into this.

Hi @PaulSchnau thanks for lettings us know about this. If you haven't already, would you please contact [email protected] as well? One thing you could try is increasing the frequency at...

Hey @sanathfp not sure if this helps you, but check out this tip we gave someone for running FullStory in a Next.js application: https://github.com/fullstorydev/fullstory-browser-sdk/issues/51