Post

Replies

Boosts

Views

Activity

Applying new snapshot to diffable data source in iOS 15 trigger unnecessary cell registration call
I try to figure out the improvement of apply(_:animatingDifferences:) function call without animation in iOS 15 Simulator. As log shown below, after removing an item and apply edited snapshot to diffable data source, it trigger several unnecessary calling to new cell that did not appear on screen. ENV: MacBook Air (M1, 2020), macOS Big Sur 11.4 (20F71) Xcode Version 13.0 beta (13A5154h), iOS 15.0 Simulator configure AlbumItemCell:(0x0000000128042400) at section:(0), item:(0) configure AlbumItemCell:(0x0000000125624aa0) at section:(0), item:(1) configure AlbumItemCell:(0x00000001280442a0) at section:(0), item:(2) configure AlbumItemCell:(0x0000000128045670) at section:(0), item:(3) configure AlbumItemCell:(0x0000000128050af0) at section:(0), item:(4) configure AlbumItemCell:(0x0000000125626430) at section:(0), item:(5) remove last items configure AlbumItemCell:(0x000000012571f970) at section:(0), item:(0) configure AlbumItemCell:(0x000000012571f970) at section:(0), item:(1) configure AlbumItemCell:(0x000000012571f970) at section:(0), item:(2) configure AlbumItemCell:(0x000000012571f970) at section:(0), item:(3) configure AlbumItemCell:(0x000000012571f970) at section:(0), item:(4)
6
0
5.3k
Jun ’21
NSURLSessionWebSocketTask return bad address error
We receive bad address error Error: (kNWErrorDomainPOSIX 错误 14 - Bad address),未能完成该操作。 Environment: iPhone 8#iOS#13.6# from completion handler in -[NSURLSessionWebSocketTask receiveMessageWithCompletionHandler:] or -[NSURLSessionWebSocketTask sendMessage:completionHandler:] I'm not quit sure which one since their reporting error from same function in our code :( =================================================== I was search information about #define EFAULT 14 /* Bad address */ and socket, most of content telling me that we did not pass buffer to socket function properly. But NSURLSessionWebSocketTask has no method for me to manipulate underlying socket. =================================================== We can not reproduce this error since it was reported from user device. Any possible reason that make this error happen?
2
0
674
May ’23