Crashlytics error code: 202 when sending files

Question

My application ( iOS ) used the crashlytics framework , and so far everything was fine. But a few days ago I did not see the alarm panel report.

So, I made a testing error [[Crashlytics shareInstance] crash] and ran

 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 application can not send an error report :(

What happened to my app?

P / s: I have another Android app, it still used the same key crash tests, and everything was fine.

Answer 1

Yes, the problem is missing in dSYM. So I changed the build version and built again ... the problem was solved!

If someone has a problem that the crashlytics application (on MAC) was frozen, so many sheep were busy, let's clear the cache on ~/Library/Caches/com.crashlytics.mac (from a crashlytics supporter )

Answer 2

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

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

Adding a build script:

• To add a Run script Build Phase in Xcode 6, select the goal of your application in your project, then select "Generate Phases".
• Click the small plus sign and select “New Run Script Build Phase”.
• You can now see the Run script section in the middle of your Build Phase options, as shown above.
• Inside the body of the Run script Build Phase, paste the script.

The above quote is taken from the Crashlytics video referenced by this post .