crash in v7.4.1, NSGenericException Task created in a session that has been invalidated

[alflix]

#25 Thread
NSGenericException
Task created in a session that has been invalidated

0
CoreFoundation
___exceptionPreprocess + 164
2
CFNetwork
_CFHostCreateWithName + 106588
3
App
__InstrumentDataTaskWithRequestCompletionHandler_block_invoke (FPRNSURLSessionInstrument.m:311)
4
App
__InstrumentDataTaskWithRequestCompletionHandler_block_invoke (FPRNSURLSessionInstrument.m:311)
5
App
VungleAdsSDK.NotificationService.sendNotification(urlString: Swift.String, key: Swift.String, attempt: Swift.Int) -> () + 1164
6
App
closure #1 ([Swift.String : Swift.Int]?) -> () in VungleAdsSDK.NotificationService.sendStoredTpats() -> () + 264
7
App
closure #1 @sendable () -> () in VungleAdsSDK.Persistence.readStoredTpats(callback: ([Swift.String : Swift.Int]?) -> ()) -> () + 836
8
App
reabstraction thunk helper from @escaping @callee_guaranteed @sendable () -> () to @escaping @callee_unowned @convention(block) @sendable () -> () (:0)

[crbinsf]

Thanks for sharing crash details here @alflix - based on trace, one follow up question - is this happen on first launch of the application, or is this happening when the application is launched a second (or greater) time?

[alflix]

Thanks for sharing crash details here @alflix - based on trace, one follow up question - is this happen on first launch of the application, or is this happening when the application is launched a second (or greater) time?

this happen within one second of first launch, and a device can crashes more than once

[UniqueSilence]

func asyncLayout() -> (@escaping(_ item: ChatListItem, _ params: ListViewItemLayoutParams, _ first: Bool, _ last: Bool, _ firstWithHeader: Bool, _ nextIsPinned: Bool) -> @escaping(ListViewItemNodeLayout, @escaping(Bool, Bool) -> Void))

there is the same error, do you have a perfect solution about the question?

[crbinsf]

@alflix - apologies for the delay in updating here - the original crash has been triaged and a fix is currently in test. This will be addressed in our 7.5.0 SDK release in January.

[vincentyao2016]

Hi @alflix
The issue has been fixed on our iOS SDK 7.4.4 which has been released. Please upgrade the SDK to fix the issue. And sorry about the issue again.