identitylookup needed for ILMessageFilterQueryHandling?

Question

Created Apr ’25

Replies 4

Boosts 0

Participants 2

My iOS app uses a Message Filter extension (via ILMessageFilterQueryHandling) and works only when run directly as the extension target. When installed normally (via TestFlight), the filter does not trigger at all — which I now believe is because iOS enforces the com.apple.developer.identitylookup entitlement at runtime.

Anyone know anything about this? I put in a request for the entitlement last week but heard nothing back. Called Apple "technical" support and they had no idea what I was talking about.

The documentation around this is EXTREMELY lacking in my opinion...

Boost

Answer 1

fraudmonitor OP

Apr ’25

Same boat! When building my target, I now get Provisioning profile "iOS Team Provisioning Profile: xxx.MessageFilterExtension" doesn't include the com.apple.developer.identitylookup entitlement.

0

Answer 2

j8thro OP

Apr ’25

Interesting. Apparently they shelved a lot of their documentation around this a few months back. Such a disapointment that we are subjected to guessing at entitlements needed, and of course the wait time for any response is weeks...

0

Answer 3

fraudmonitor OP

Apr ’25

I added logging to the ILMessageFilterCapabilitiesQueryHandling and it is not getting called.

    func handle(
        _ capabilitiesQueryRequest: ILMessageFilterCapabilitiesQueryRequest,
        context: ILMessageFilterExtensionContext,
        completion: @escaping (ILMessageFilterCapabilitiesQueryResponse) -> Void
    ) {
        os_log("Handling capabilities query", log: self.logger, type: .debug)
        let response = ILMessageFilterCapabilitiesQueryResponse()
        response.transactionalSubActions = [.none]
        response.promotionalSubActions = [.none]
        completion(response)
    }
   ...
}

0

Answer 4

j8thro OP

Apr ’25

Yes same issue for me the filter extension never gets called by the main target so no logs to go by

0