I am implementing an Unwanted Communication Reporting Extension (IdentityLookupUI) to allow users to report spam messages to our backend.
The extension works perfectly in terms of data collection and network reporting (using ILClassificationExtensionNetworkReportDestination). However, I’ve encountered an issue with the message lifecycle: whenever the user taps "Done" and I return a response, the system automatically moves the reported message to the Recently Deleted folder.
I want to report the data but keep the message in its current folder (especially when the user classifies it as "Safe"). I have tried varying the ILClassificationAction, but it seems the system ignores the action in favor of "cleaning up" the thread.
Example of my current implementation:
override func classificationResponse(for request: ILClassificationRequest) -> ILClassificationResponse {
// Even when returning .none or .reportNotJunk
let action: ILClassificationAction = (self.type == "spam") ? .reportJunk : .none
let response = ILClassificationResponse(action: action)
response.userInfo = ["type": self.taggedType, "sender": self.sender]
return response
}
My Questions:
Is there a specific ILClassificationAction or userInfo key that tells iOS not to move the message?
Is this movement a mandatory "post-report cleanup" behavior of the IdentityLookup framework that cannot be overridden?
Does anyone know a workaround to report the communication while maintaining its original location in the Messages app?
