Only log in Debugger, but no data in report

Question

I'm now testing my project with TestFlight, I can see some logs (including checkpoint, session_start, etc) in SDK Debugger, but my reports are empty in Build. I send email to support#testflightapp.com, asked the question on Twitter, and even checked the tweets listed, but still cannot find the solution..I think SO is the only site I can refer to help now..

Have anyone met this issue before & solved now?? And btw, where is the TFLog? I cannot find any debug log that I set.

Thanks in advance!

---

EDIT:

Here're two screenshots that will show my issue clearly.

You see, I sent feedback, checkpoints (and there're also some session_stard/end logs), but no detail report. :(

---

SDK Debugger: The TestFlight SDK Debugger lets you see your team's SDK data before it hits our queues. The console also shows orphaned SDK events which can help you confirm you have implemented the SDK correctly.

So I think I implemented the SDK correctly. I tried both SDK v1.0 & v.0.8.3, and I build a new project for testing this service, same result.

How I wish I can offer bounty now!! Please help..

Answer 1

Finally, I got a reply from Testflight team:

To be blunt we've been having some stability issues which seem like they're the root cause of your trouble. The team is working as fast as they can to bring you a faster, more stable TestFlight.

unfortunately..

---

And I found the TFLog (tested reports from my simulator, but cannot receive reports for my device yet):

1. choose your desired build in Builds section;
2. choose Sessions in Reports section;
3. choose a desired tester, and you'll find some logs like:
   

4. click the blue INFO icon to open a detail dialog:
   

5. and at the top right corner, you'll find a Events button, click to open a selection area, then just select the Log and you'll get the TFLogs.

Answer 2

Just a heads up for anyone experiencing issues with the Testflight SDK not logging events at all.

Double check if you are also using Flurry for Analytics and see if disabling it solves the problem (it did for me). I read somewhere that this is a known issue with the way exception handlers have been implemented on Testflight SDK.