Unfortunately no. Sorry, i misclicked the button mark as accepted answer there.

I see, so it's confirmed that there's nothing we can do to resolve this issue in my side for now beside waiting for the fix to be published on the next iOS update by Apple (even though we are not sure when and on which version). Thanks for clarifying that for me, Quinn. Really appreciate your help ! Please do send my thanks to your colleague for pointing out one of crucial part in this investigation. XD Have a nice day, both of you !

hi, is there any updates that can be shared from the Apple side regarding this ? like maybe it will be fixed in the upcoming iOS 16 ?

If i understand it correctly, you mean if it still occurs in iOS 16, I should submit a new bug report and mentioned about the existing one there (which is FB9839142) and also let you know again both of the bug report numbers here, right ?

Noted, thanks. Will do that later.

Hi, I've checked again after iOS 16 beta released and found out that the similar crash still exists but this time the stack trace pointed to different suspect but still about unrecognized selector issue with stack trace that pointed to none of our internal project code. I've filed a new bug report that contains crash reports in it too with number FB11204498 and also already included the previous bug report number (FB9839142). Looking forward to your update on this.

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.

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 !

I’ve seen a number of reports about that recently. I’d appreciate you posting the details to this thread. Noted, I'll post the details later there. Can you double check the range of OS releases where you’re seeing this crash? Ah, that was a miss on my side, my apologies. I rechecked again just now and it seems to start since 17.2.0.

I tried to post a crash report earlier but failed. This is the example of the crash report that I tried to attach: https://file.io/6r7MyCe2llIK

Oh I am sorry, I tried to download the file earlier to make sure the link actually works but I didn't notice there was a note in the site that says: File will be deleted after download. I have reuploaded again, please check this one: https://file.io/4Xmdqsw99fJh

Anyway, I don’t think there’s much you can do about this, other than to file a bug (which you’ve already done). Also, please monitor your crash reports to see if any start coming in from 17.4. Noted, thanks for the explanation. I just checked again and there was 1 incident happening in iOS 17.4 on 24th February 2024. So in other words, I can only wait for the fix in upcoming iOS versions ya. Swizzling on classes you don’t own, like UIView, is not the path to long-term binary compatibility. Thanks for the advice. It seems that the code comes from 3rd party SDK that we used. Will try to review with the team again regarding this.

Test to upload crash report crash-log-iOS-17.crash

You were right, I was able to upload it here. Actually last time, I only tried to upload it when trying to create the initial post, not through reply section. I wonder if that could be the factor to this issue or the logic used there should be the same with reply section ?

Got it. So I tried to create a new thread here but I was able to attach the crash report just fine. Now I am more confused why it didn't work few days earlier. The only case I can think now is someone maybe accidentally mess up the logic earlier then fixed it, that's why it works now.