Post not yet marked as solved
This is a testing thread to try attaching crash report that was unable to be attached few days earlier when I tried to create a new thread. This test is requested by Apple DTS to help isolating the issue.
For more context: https://forums.developer.apple.com/forums/thread/747480
Crash report:
crash-log-iOS-17.crash
We found crash reports from Xcode organizer about some crashes happening only in iOS and iPadOS version 17.3.0 and later across all our releases mostly in background state related to Network SDK.
Unfortunately, we are unable to reproduce the issue. On the crashed thread, it seems to refer to process from Network SDK but we never import and use it directly in our project.
Most of the functions found in the main thread in the crash report can't be accessed from the project, it seems to be internal framework calls in iOS SDK. The crash pointing to this line of code: nw_protocol_error
Bug number: FB13661192
Somehow I cannot attach any crash report here, it always return error This post contains sensitive language. Please revise it in order to continue. whenever I try to submit it. If I remove it, I can submit the post.
Post not yet marked as solved
We are currently observing AVPlayerItemNewErrorLogEntry notification event to track error from AVPlayer which later will be written in our logs to help us identify issue in production.
But when we checked again, turns out currently the notification is not getting triggered causing many missing crucial information in our logging to debug issue that occurred related to AVPlayer as we need the errorComment information inside the error log event. Meanwhile, the accessLog event get triggered just fine.
But if we check the error directly, it said that the errorLog is not empty and we can retrieve the errorLog manually by accessing the errorLog from AVPlayer.currentItem directly. (can refer to the screenshot below regarding the error from console)
Is there something wrong with our implementation or it is indeed a bug from Apple ?
We already filed bug report with number: FB12580746 and we are using Xcode 14.3.1.
Hi,
Our application is currently crashing in production, only for users with iPhone and iPad running iOS and iPadOS 15 through all releases. Unfortunately, we cannot reproduce the issue, neither through direct build from Xcode or using build from app store, so it seems to happen intermittently.
From third party crash analytics, it seems to happens mostly of background and they highlighted this as the issue.
Fatal Exception: NSInvalidArgumentException
-[_NSXPCDistantObject cleanupWithCompletionHandler:]: unrecognized selector sent to instance 0x2813293b0
From the Xcode crashlogs, it highlighted this which intrigue me a bit and it also exists on the stack trace from the third party (you can see they call a same function __cleanupWithCompletionHandler there).
5 Pegasus __58-[PGPictureInPictureProxy __cleanupWithCompletionHandler:]_block_invoke
It seems that the crash happens probably because some process related to PIP feature that triggered this function that is handled by Pegasus framework.
Any idea why this happens and is there anything i can do to prevent the crashes from happening again ?
crash-log-iOS-15.crash
edysudarto.