Possible Memory Leak in RoktHTTPClient.init(sessionConfiguration:encoders)

[RGG-jayoung]

We've been profiling our app for memory leaks and see this issue pretty consistently:

This occurs when we call the Rokt SDK set up code from the default documentation.

We are seeing this in all versions of the SDK between 4.3.0 and 4.4.0.

Steps to reproduce:

1. Follow the Rokt documentation to set up your SDK.
2. Profile your app using Instruments, choosing the Leaks template
3. Run your app through its standard startup process, you don't need show Rokt UI, just to call the SDK set up methods.
4. Filter the memory leaks by the word session. A few may appear.

[jamesnrokt]

Hey @RGG-jayoung!

Thanks for reaching out and providing info on this potential memory leak and giving reproduce steps, really appreciate it.

One of our iOS engineers triaged this by profiling the SDK directly, but unfortunately they were unable to reproduce.

Wondering if you can provide a little more information / confirm the assumptions below:

• SDK version: 4.3.0, 4.3.1 & 4.4.0

• XCode version: Assumed 15

• Swift version: Assumed 5

• Where and how are you initialising the SDK within your application Assumed From your description we're assuming it was in an equivalent of AppDelegate.swift didFinishLaunchingWithOptions

• If relevant what method are you calling to experience the bug and how are you calling it Assumed You only interacted with Rokt.initWith(...) and no other methods