Your "Associated Domains" entry should be: classificationreport:<your fully qualified domain>

Update 17:00 GMT+7 05-Feb-2022 I have just found that if I force close the iOS Messages app, the report can be sent to my external server again. It means if I want to continue reporting, I have to force close the iOS Messages app first. Does it mean there is something unfinished in the last workflow?

Hi Rico, Though I press "Cancel" in the iOS Messages application to end a session (according to my understanding), I must force close the iOS Messages application to make it work again. I update steps to reproduce: Install the app contains a Message Filter extension and an Unwanted Communication extension Enable those 2 extensions in Settings (Phone and Messages) Open the iOS Messages app Open a communication thread Press and hold a SMS message Press "More..." Press "Report Messages" Press "Done" button when that button is available on GUI of the reporting extension Press "Cancel" button in the iOS Messages application after the GUI of the reporting extension is dismissed Repeat from step #5 with another SMS Expected result: There are 2 reports sent to the external server Actual result There is only one report sent to the external server (step #8)

I have filed a bug report FB9905746 in case anyone else experienced this problem too.

I would like to update some information: STEPS TO REPRODUCE 1. Install the app contains a Message Filter extension and an Unwanted Communication extension 2. Enable those 2 extensions in Settings (Phone and Messages) 3. Open the iOS Messages app 4. Receive a SMS from an unknown phone number A 5. Press and hold the SMS message received in step 4 6. Press "More..." 7. Press "Report Messages" 8. Press "Done" button when that button is available on GUI of the reporting extension 9. Press "Cancel" button in the iOS Messages application after the GUI of the reporting extension is dismissed 10. Receive a SMS from an unknown phone number B 11. Press and hold the SMS message received in step 10 12. Press "More..." 13. Press "Report Messages" 14. Press "Done" button when that button is available on GUI of the reporting extension 15. Press "Cancel" button in the iOS Messages application after the GUI of the reporting extension is dismissed When check device log I see in the first try (step 8), the process MessageFilter appeared but not in the second try (step 14) com.apple.IdentityLookup.MessageFilter classification report request: <private> ... com.apple.IdentityLookup.MessageFilter Garbage collection for alternative services

Update 15:00 GMT+7 01-Mar-2022 I have tested on another iPhone 11 Pro Max but iOS 14.8.1: I can send the 2nd report, the 3rd report... and so on without doing force close the iOS Messages application But the GUI created by the Unwanted Communication Extension is not displayed immediately (5-6s delay)

Sorry, I don't have any iOS 14 device now to reproduce. I also required iOS 15 is the minimal OS version. Actually, after publishing the app to TestFlight and App Store, this issue didn't appear.

Same here. I use SwiftUI TextField and TextEditor. When the keyboard appears, CPU and memory usage suddenly increase. The extension will crash when memory usage of the extension exceeds its limit 50MB. EXC_RESOURCE RESOURCE_TYPE_MEMORY (limit=50 MB, unused=0x0) This issue doesn't happen in iOS 15 and early version of iOS 16. But now I see it in iOS 16.0.3 and 16.3.1 at my end.

I wonder this issue relating to this one https://developer.apple.com/forums/thread/713490

Update from me: This issue seems not happen in the iOS 16.4 beta (20E5239b).

Update from me: This issue seems not happen in the iOS 16.4 beta (20E5239b) I tested on iPhone SE 2020. An interesting thing is that the memory leak issue doesn’t happen on iPhone SE 2020 though official iOS 16.3.1 (20D67) or iOS 16.4 beta (20E5239b).

Update: still happen on my iPhone 12 Pro iOS 16.4 (20E247)

Thank for your confirmation, Eskimo! I can remove this workaround from my list now.