Using TrackJs in a callback about trackjs-package HOT 8 CLOSED

Hey @Shomari, thanks for reaching out. When you call trackJs.track(), we attempt to make the value you pass into an Error object so that we can see a stack trace. If the data you send is unserializable, it could prevent an error from sending, or send a different error than what you expect.

Can you share some example code of what you are seeing? Can you share what data_i_want is at the time you invoke track?

from trackjs-package.

@toddhgardner even if I just put in a simple string then nothing happens. This issue only happens in the callback method and not anywhere else. In the example code, the first trackJs.track will fire, but the second one that is in the callback messageListener (with the string 'in callback') won't fire

  signAgreement(){
    var that = this;
    trackJs.track('first')
    HelloSign.init(client_id);
    HelloSign.open({
      url: sign_url,
      allowCancel: true,
      messageListener(eventData) {

        trackJs.track('in callback')
        var eventMessage = eventData.event;
        var signatureId = eventData.signature_id;
          that.props.onHide();
          NotificationActions.success('Document successfully signed');
        }
      },
    });
  },```

from trackjs-package.

@Shomari I'm not aware of any situation in our script that would know the difference, or care at all between these two calls. Are you confident that the callback is firing? If you attach a debugger, or print a console message, do you see it firing?

from trackjs-package.

yup, I've put debugger in and have console logged the data with success. Also our notificationAction also fires. Its just that we don't get any data showing up on my.trackjs.com for our account

from trackjs-package.

@Shomari can you email us your account name or email address so we can dig in further? [email protected].

Have you created a clientside filter using the onError callback?

from trackjs-package.

Just so you all aren't spinning your wheels we think its because browserfiy or something else thats preventing trackJs from firing (we keep getting entity too large errors) so we doubt it has anything to do with the trackJs code

from trackjs-package.

@Shomari thanks for the update!! You may receive an Entity too large from us when sending an error if the text is more than 100kb. We do this to protect our system against high volume and attack.

If you have lots of very large objects getting logged to the console, it is possible you hit this limit.

from trackjs-package.

yeah we aren't directly sending large objects but think something else maybe hijacking the call and adding stuff to it. Thanks for your responsiveness

from trackjs-package.