Crashlytics error code: 202 when Submitting files

Question

My app (iOS) used crashlytics framework and it was OK until now. But in some days ago, I didn't see any report on crashlytics dashboard.

So I made a testing bug by [[Crashlytics shareInstance] crash] and it logged

2013-08-12 15:02:22.927 ... [Crashlytics] Processed file successfully
2013-08-12 15:02:22.930 ... [Crashlytics] Alternate file submission complete
2013-08-12 15:02:22.933 ... [Crashlytics] Displaying permission alert
2013-08-12 15:02:38.919 ... [Crashlytics] Submitting files
2013-08-12 15:02:41.585 ... [Crashlytics] Submission response: {status: 202, error: (null)}
2013-08-12 15:02:41.587 ... [Crashlytics] Submitted file successfully
2013-08-12 15:02:41.589 ... [Crashlytics] No sendable files, submission process complete

Now, my app can not send any bug-report :(

What happened with my app?

P/s: I have another Android app, it still used same key-crashlytics and it was still OK.

Answer 1

Yeah, the problem is missing of dSYM. So I changed build version and build again.... problem was solved!

If anybody has the problem is that crashlytics app (on MAC) was freezed, took so much ram, let clean cache at ~/Library/Caches/com.crashlytics.mac (from crashlytics supporter)

Answer 2

We recently ran into this issue and I found that somewhere along the way the build script was removed. Adding it back in with the following fixed the issue for us:
./Crashlytics.framework/run <your_api_key> <build_secret>

Note : When using Cocoapods you will want to us the following instead of the above (source): ./Pods/CrashlyticsFramework/Crashlytics.framework/run

Adding a build script:

1. To add a Run Script Build Phase in Xcode 6, select your application target in your project, then select "Build Phases".
2. Click the small "plus" icon and select "New Run Script Build Phase".
3. You should now see a Run Script section in the middle of your Build Phase options, as shown above.
4. Inside the body of the Run Script Build Phase, paste in the script.`

The above quote comes from the Crashlytics visual tutorial, referenced in this post.