shareText

actual fun shareText(text: String)(source)

Shares text through the platform share sheet.

Implemented on Android (ACTION_SEND chooser) and iOS (UIActivityViewController). JVM and wasm are no-ops: neither platform has a share sheet to call, so there is nothing to implement and nothing being hidden. There is no capability flag for text because the only platforms where this does nothing are the two where nothing could be done — contrast canShareImage, which reports a gap that is host-app-fixable.

expect fun shareText(text: String)(source)

Shares text through the platform share sheet.

Implemented on Android (ACTION_SEND chooser) and iOS (UIActivityViewController). JVM and wasm are no-ops: neither platform has a share sheet to call, so there is nothing to implement and nothing being hidden. There is no capability flag for text because the only platforms where this does nothing are the two where nothing could be done — contrast canShareImage, which reports a gap that is host-app-fixable.

actual fun shareText(text: String)(source)

iOS actual: UIActivityViewController, the counterpart to Android's ACTION_SEND chooser.

This was actual fun shareText(text: String) {} — an empty body with no capability flag, so an iOS user got a share button that did nothing and the caller had no way to detect it. jvmMain and wasmJsMain keep their empty bodies because no share sheet exists on those platforms; iOS has one, which made the no-op a false claim rather than an honest gap.

Ported from Doori's IosShareSheet (core/platform), which is the same 24 lines already running in the family.

actual fun shareText(text: String)(source)

Desktop has no system share sheet, so there is nothing to invoke: the JVM actual is a deliberate no-op rather than an unfinished function. A desktop host that wants sharing copies the text to the clipboard itself — that is a host decision, not something this module should guess at.

actual fun shareText(text: String)(source)

Deliberate no-op. The Web Share API (navigator.share) is available only on a secure origin, only from inside a user-gesture handler, and not at all on most desktop browsers — calling it from here would throw on the majority of hosts. Wiring it up properly means routing the call through the host's gesture handler, which is a change to this module's contract, not a fix.