recordUserDetails - NSURLConnection delegate thread problem about countly-sdk-ios

[dieskim]

For now I have come up with a TEMP fix

It basically does the same as what is done with crash reports

dieskim@0f2e338

But I believe that if it fails

if (error || !recvData)

it will cause all event sending to pause. I believe this will happen for crash and events as well.

[dieskim]

Also it seems that connectionWithRequest:delegate has been Deprecated in iOS 9.0.

https://developer.apple.com/library/prerelease/ios//documentation/Cocoa/Reference/Foundation/Classes/NSURLConnection_Class/index.html#//apple_ref/occ/clm/NSURLConnection/connectionWithRequest:delegate:

[erkanyildiz]

Actually I have tried all these combinations. No problem at all.

Picture existence

• none
• only kCLYUserPicture (on web)
• only kCLYUserPicturePath (on device)
• both kCLYUserPicture & kCLYUserPicturePath

Picture file format

• JPG
• PNG
• GIF

Before / after recording other events

Internet connection available / not available (sending later in next session)

Real Device / simulator

Now I think this is a Titanium issue.
Just like that Open-UDID problem.

[erkanyildiz]

Your temp fix has no good use. It is a special case where SDK sends a synchronous request for delivering crash report just before application is terminated. You must not use it for sending user details, as it will cause the app to be unresponsive while that request is going on, and it is impossible to upload profile picture that way.

[dieskim]

Simular issue - https://developer.appcelerator.com/question/122673/nsurlconnection-in-ios-module

[erkanyildiz]

Currently NSURLConnection deprecation in iOS9 is not a problem. We will be using NSURLSession instead of it in the future anyway.

[dieskim]

Ok I might have a solution - needs some more testing

https://developer.appcelerator.com/question/144514/module-development----nsurlrequest

Adding the following macro

ENSURE_UI_THREAD
Info the proxy function that calls recordUserDetails seems to fix it..

[erkanyildiz]

According to our tests with native app, this looks like a Titanium related issue.