Crash reporting broken about countly-sdk-ios

[erkanyildiz]

Hi yuri,

Thanks for contacting.

1. It looks like it is a problem with try server. My test server (16.02.01) works fine with POST. No need to modify something. If you send me an email I can share server details, so you can test :)

2. For now, Crash Reporting and Push Notifications does not comply with our latest SDK Development Guide, refactoring and updating is still in progress. You can see these are the only parts still using NSURLConnection instead of NSURLSession. That is why server response is not checked for that success dictionary. Currently, if there is an error or if there is no response, it is considered crash report could not be delivered.

3 & 4) After the SDK update, saveToFile will be called synchronously for both CrashReporting and applicationWillTerminate callback, so there will be no problem.

By the way, I am on vacation now. I will continue working on them early May.
So, I can say roughly estimated time for these updates are mid May.

Thanks again.

[ar2rsawseen]

Hello,
I will recheck try server and get back to you.

[yuriy128]

Btw, i was testing against Countly's enterprise cloud server, this should
always work.
On Mon, Apr 25, 2016 at 2:06 AM Arturs Sosins [email protected]
wrote:

Hello,
I will recheck try server and get back to you.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#79 (comment)

[ar2rsawseen]

Hello,
just retested try.count.ly, cloud.count.ly and test server and all work correctly with post.
Can you provide any specific steps to reproduce this?

[yuriy128]

Hmm, didn't do anything special, but i was basically getting "missing
app_key or missing device_id" error. Maybe there are some nodes on
try.count.ly that are running old server code? I will try again in the
morning.
On Mon, Apr 25, 2016 at 3:50 AM Arturs Sosins [email protected]
wrote:

Hello,
just retested try.count.ly, cloud.count.ly and test server and all work
correctly with post.
Can you provide any specific steps to reproduce this?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#79 (comment)

[ar2rsawseen]

Could it be some ios version specific, that server does not understand post data?

[yuriy128]

Was getting a very specific message, testing with your own "testCrash"
method.
On Mon, Apr 25, 2016 at 4:56 AM Arturs Sosins [email protected]
wrote:

Could it be some ios version specific, that server does not understand
post data?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#79 (comment)

[yuriy128]

Do you guys have access to the logs from the enterprise try server, you should be able to see requests coming in yesterday that had this issue. I tried today with DHC plugin and the POST request works now. Which makes me believe that you might have an out of date server somewhere that is causing this issue. The other issues: #2,#3,& #4 still apply.

[erkanyildiz]

Hi again,

This commit solves #3 and #4
erkanyildiz@34eb96e

#2 will be solved too when refactor finished.

I will merge it on main repo when all finished.
Thanks.

[erkanyildiz]

And this fixes #2:
e20c344

Soon I will merge to main repo.

Thanks again.