INSendMessageIntent does not implement UNNotificationContentProviding

[Brendonovich]

Although it's not documented, it seems that INSendMessageIntent is supposed to implement UNNotificationContentProviding as seen in a bunch of code here on github.
I'd like this as I'm attempting to call UNNotificationContent::contentByUpdatingWithProvider_error with an INSendMessageIntent which should be valid as far as I can tell.

[madsmtm]

Those impls were semi-intentionally not provided, as it requires either objc2-intents to depend on objc2-user-notifications, or the other way around, and I'm not sure which direction is the most desirable? See

objc2/framework-crates/objc2-intents/translation-config.toml

Lines 15 to 17 in 81bc841

	# Unsure whether this should depend on UserNotifications, or vice-versa
	class.INSendMessageIntent.skipped-protocols = ["UNNotificationContentProviding"]
	class.INStartCallIntent.skipped-protocols = ["UNNotificationContentProviding"]

I'm unfamiliar with both of those frameworks, maybe you can help provide context for which dependency relationship would be desirable?

[madsmtm]

In the meantime, you should be able to do something like:

fn as_protocol(msg_intent: &INSendMessageIntent) -> &ProtocolObject<dyn UNNotificationContentProviding> {
    // SAFETY: `INSendMessageIntent` implements the `UNNotificationContentProviding` protocol,
    // even thoough it doesn't currently implement the trait: https://github.com/madsmtm/objc2/issues/814
    unsafe { std::mem::transmute(msg_intent) }
}

let content = as_protocol(msg_intent).contentByUpdatingWithProvider_error(provider).unwrap();

[Brendonovich]

Oh awesome, thankyou! I'm not well-versed enough to say which direction the dependency should go, sorry.