21

I integrated testflight sdk in the app to collect analytics and I am getting a leak which points somewhere in the code written in the files I imported to integrate the sdk.

Attached is the screen showing the information about the leak.

Any advise?

none

Kara
  • 6,115
  • 16
  • 50
  • 57
adi27
  • 509
  • 1
  • 3
  • 10
  • Just tested my app that uses testFlight for this leak and I have it too. We'll have to see what testFlight says. – Kyle Rosenbluth Apr 04 '12 at 14:13
  • This has been around for a really long time I believe. Let me know what you find out! – bogardon Apr 11 '12 at 19:30
  • 2
    Hey I wrote my query to testflight and they say this: "I asked a tech about this and he said it's not a leak, but it's memory we use for the length of the application. It is something we can improve on and we'll certainly work on that as we have time." – adi27 Apr 13 '12 at 03:10
  • Leaks for me too.Its probably OK given the above answer, and that its a tiny amount of memory leaked, though I am sure they could avoid it showing as a leak if they tried! This was enough to dissuade me from using the TestFlight SDK – Peter Johnson Apr 18 '12 at 12:56
  • Set a 'breakpoint' and see where the leak might be, would be a start. – Aleksander Azizi Jul 18 '12 at 19:04

2 Answers2

2

Keep the testflight integration code with in debug constant so that it will not leak in when your App is online. this may help you only when your app need to collect the analytics data while testing or dev stage. 

    #ifndef DeBUG 

    // integration code here
    #endif

Note: you need to make sure the per-processor macro is added in the build settings for debug configuration.

Ramakrishna Guttha
  • 762
  • 1
  • 12
  • 24
0

TestFlight has just released SDK v1.3.0-beta2.
In this version the memory leak seems to be resolved.

You can get it here:
https://testflightapp.com/sdk/download/

For CocoaPods users, I've submitted a new podspec for this version.

Yvo
  • 18,681
  • 11
  • 71
  • 90