User Profile

Posts

Posts

Post not yet marked as solved
10 Replies
Replied In Assistance with back trace
I feedback from the bug I filed with apple. The most likely cause is that the CFSocketStream has been overreleased by the app. CFSocketInvalidate should not cause SocketStream to be deallocated inline since it took an extra retain on itself before calling CFSocketInvalidate.
Post not yet marked as solved
10 Replies
Replied In Assistance with back trace
Hi @eskimo Your thorough investigation is appreciated. For context I am using rabbit client. This library uses GCDAsyncSocket. Unfortunately we are bound to use this library for the medium term because of the development effort required to modify our comms with our backend services. I filed a bug using Feedback Assistant. The reference is FB13091139
Post not yet marked as solved
10 Replies
Replied In Assistance with back trace
My app would have no crashes if it were not for this crash. On average the crash occurs 5 times a week. The most recent version of iOS this crash has happened on is 16.6. It looks like it has occurred on every version of IOS 16. I've added a crash log for iOS 16.6 Crash Log iOS 16.6
Post not yet marked as solved
10 Replies
Replied In Assistance with back trace
Hi @eskimo Thanks for the reply. I've attached the crash log which I took from XCode. Any assistance is greatly appreciated Crash Log
Post not yet marked as solved
10 Replies
Replied In Assistance with back trace
The backtrace was too large to add so I've added it in its entirety here https://pastebin.com/SmrpwrkY
Post marked as solved
5 Replies
Replied In iOS 15 crash: Fatal Exception: NSInternalInconsistencyException Invalid parameter not satisfying: pos
In my case this was caused by users copying and pasting into a UITableView Form. The solution was to not use cell reuse. This can be easily accomplished by adding something like the row number to the cell identifier string.