Brian Nickel

The issue is likely that `Heap.withReactNavigationAutotrack` is being called inside a function (likely `App`). Any time that `App` executes, `HeapNavigationContainer` is a new component class causing the whole navigation container...

This is an embarrassing mistake on my end. I broke logging to production by implementing some test functionality. There's a fix incoming, but a temporary workaround is to add an...

@MudassarSharifSandhu You'll need to rebuild if you haven't already. The heap.config.json file gets built into the app as part of the iOS build process. @abriandev Can you try rebuilding your...

@abriandev You may try running `pod install` in the ios directory to see if that does anything. Android and iOS both consume the config file through build processes and native...

How are you using `Heap.withHeapIgnore` in your app? The function doesn't modify the component but outputs a new one. I was able to accomplish most of what you're looking for...

Sorry I missed this reply. The code you're using would prevent navigation and touch events, but it doesn't disable Heap. When Heap is initialized, it sends out an initial pageview...

Close could also detach the delegate to reduce the risk of a memory leak.