[SKAdNetwork startImpression:completionHandler:] hangs current thread

Question

Created Apr ’21

Replies 4

Boosts 0

Views 1.2k

Participants 3

We are implementing a new view-through attribution in our SDK.
But we have a weird issue with startImpression:completionHandler: static method of SKAdNetwork class. It seems like it just blocks current thread execution without calling completionHandler. It doesn't matter if this method was called on main thread or on background thread.
Also when we were missing some required fields in SKAdImpression object, completionHandler was called with corresponding error message and thread execution wasn't blocked.

Does anyone else has the same issue?

We are using latest XCode 12.5 and iPhone X with iOS 14.5. Both are final, not betas.

Answered by seung min in 675755022

Hello, I checked and found out that there was a problem with 14.5
But there is no problem with 14.5.1, so I think there is a problem with 14.5 version.
I'm not using the latest version of the ad SDK because it uses the latest ad SDKs.

Boost

Answer 1

jholliday_twitter OP

May ’21

Hello. We turned our use of this API on today and within a few hours had lots of crashes from the main thread hanging on it. We want to move on this API, but it's not marked as threadsafe (nor does it make sense for it to be, given what it's for) and it causes our app to crash more than 10x as often as it normally would.

I also am curious if there are any updates about this API.

1

Answer 2

seung min OP

May ’21

Accepted Answer

Hello, I checked and found out that there was a problem with 14.5
But there is no problem with 14.5.1, so I think there is a problem with 14.5 version.
I'm not using the latest version of the ad SDK because it uses the latest ad SDKs.

1

Answer 3

pavlo.kurliandskyi_startapp OP

May ’21

jholliday_twitter, thanks for your reply. Good to know that we were not alone with this issue.

seung min, exact the same situation for us. Once we updated test devices to 14.5.1 everything works. Wondering how such an obvious issue could happen in final 14.5, not a beta one.

0

Answer 4

jholliday_twitter OP

May ’21

FWIW we still encounter this issue on 14.5.1. The only way we've been able to avoid the damage is by dispatching async to (non-main) serial dispatch queue.

0