Crash on iOS 15 devices happens mostly in background

Question

edysudarto OP

Created Jan ’22

Replies 17

Boosts 1

Views 9.5k

Participants 7

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

Answered by DTS Engineer in 700787022

Do you have access to the source code referenced in the crash report? If so, what does the code around line 1240 of PGPictureInPictureProxy.m look like?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

edysudarto OP

Sep ’22

Hi, i've checked again and apparently the crash happens on 15.7 also (regarding bug report FB11204498).

Do you think I should create a new thread regarding this since the stack trace pointed to different suspect or just continue with this thread and add the crash log here too since the crash issue seems relevant and the stack trace pointed to unknown codes outside of our project ?

I was wondering if there is any updates that can be shared about this since I haven't got the response from the reports since.

0

Answer 2

edysudarto OP

Oct ’22

Hi, since the main issue is already resolved in iOS 16 and already found other workaround for the other issue, I think can close this issue already

Thanks for the help so far !

0