Bug Reports

The Avo debugger doesn't behave well if the app emits the same event with the same timestamp. You may see duplicates and these cannot be expanded.

When I added this event via inspector, it came with the wrong set of properties. I removed a number of properties in the event, but the 'track changes' still displays the original properties that were added. (see screenshot)

1) Go to branch 2) Click on 'show main changes' 3) It's blank

Hi, we have 1 admin and 3 editors in our project, but in Workspace settings I'm being told we have 6 "members".

Hello, I cannot load diff for that branch. https://www.avo.app/schemas/ztYn85lzaVEu5ASjzmrG/branches/XEjT2tgTD/diff

https://www.avo.app/docs/explore-tracking-plan/download-or-copy-avo-file-manually Still points to Avo Functions which are renamed to Avo Codegen

It’s super easy to reproduce. Checkout a branch, Go to Settings > Export. Look at the downloaded JSON. It has undefined branch name. I believe same issue persist if you use public APIs to fetch it. When you export tracking plan from a branch other than main the first property shows undefined branch. { "name": "Exported Tracking Plan: undefined", ... }

Check out a feature branch, 'avo-test', by avo checkout avo-test Generate code using avo pull Bug: Avo cli automatically switch back to main branch before pulling. Therefore I cannot test changes on avo-test before merging to main. This is a new issue from upgrade.

hey. we created a source for Rescript web application and it sends the data to segment destination. I am doing this: Avo.initAvo(~env=#dev, ~segmentSothebysWebDestination=inspectorCustomDestination, ()) and you could see that there is a required property called segmentSothebysWebDestination and according to the Rescript code the type of this is the following: type avoCustomDestination = { make: (avoEnvType, option(string)) => unit, logEvent: (string, Js.Json.t) => unit, logPage: (string, Js.Json.t) => unit, revenue: (float, Js.Json.t) => unit, setUserProperties: (string, Js.Json.t) => unit, identify: (string) => unit, unidentify: unit => unit, setGroupProperties: (string, string, Js.Json.t) => unit, addCurrentUserToGroup: (string, string, Js.Json.t) => unit, logEventWithGroups: (string, Js.Json.t, Js.Json.t) => unit }; it means that all properties are required but in your doc here: https://www.avo.app/docs/implementation/reference/javascript#destination-interface-example you could see that some methods are optional like (make, revenue, setGroupProperties etc) is it a bug in your code for rescript? because for exmaple in Typescript code all properties are optional

In a working branch (not main), associate multiple sources (source "A", source "B", and source "C") to an event, then check the diff details, only one source is linked instead of multiple.