Hello Apple Developer Support,
We are using ILMessageFilterExtension with the IdentityLookup framework to classify carrier messages.
We have already verified that the Message Filter extension is invoked for RCS messages. Our remaining question is specifically about end-to-end encrypted RCS messages on iOS 26.5.
Could Apple please clarify the expected behavior for RCS E2EE messages?
- When an RCS conversation is end-to-end encrypted, is
ILMessageFilterExtensionexpected to receive anILMessageFilterQueryRequestcallback? - If the extension is invoked for RCS E2EE, does
ILMessageFilterQueryRequest.messageBodycontain the decrypted message body locally on device? - If the extension is not invoked for RCS E2EE, is this expected behavior because the message content is end-to-end encrypted?
- Is the behavior different based on carrier, region, or RCS encryption availability?
- Is there any public Apple documentation that explicitly describes IdentityLookup / Message Filter behavior for RCS E2EE messages?
Environment:
- iOS version: 26.5
- Framework: IdentityLookup
- Extension:
ILMessageFilterExtension - API:
ILMessageFilterQueryHandling.handle(_:context:completion:) - Confirmed behavior: Message Filter extension is invoked for RCS messages
- Question: Whether the same behavior applies to end-to-end encrypted RCS messages
We need this clarification to finalize expected product behavior and test coverage for RCS E2EE message filtering.