Expo 分享 iconExpo 分享

一个提供与其他应用共享和接收数据功能的库。

Android
iOS
Web
Included in Expo Go
Bundled version:
~55.0.11

expo-sharing 允许你直接与其他兼容的应用共享文件,并接收来自其他应用共享的兼容数据。

网络上的共享限制

🌐 Sharing limitations on web

  • expo-sharing 网页版是基于 Web Share API 构建的,而该 API 仍然只有非常有限的浏览器支持。在调用它之前,请务必使用 Sharing.isAvailableAsync() 检查该 API 是否可以使用。
  • 网页需要 HTTPS:只有在通过 HTTPS 提供页面时,Web Share API 才能在网页上使用。使用 npx expo start --tunnel 运行你的应用以启用它。
  • 网页上无法共享本地文件:通过 URI 共享本地文件在 Android 和 iOS 上可行,但在网页上不可行。你不能在网页上通过 URI 共享本地文件——你需要先将文件上传到某个地方,然后共享该 URI。

安装

🌐 Installation

Terminal
npx expo install expo-sharing

If you are installing this in an existing React Native app, make sure to install expo in your project.

应用配置中的配置

🌐 Configuration in app config

如果你在项目中使用配置插件(连续原生生成 (CNG)),可以使用其内置的 配置插件 来配置 expo-sharing。该插件允许你配置无法在运行时设置并且需要构建新的应用二进制文件才能生效的各种属性。如果你的应用使用 CNG,那么你需要手动配置该库。

🌐 You can configure expo-sharing using its built-in config plugin if you use config plugins in your project (Continuous Native Generation (CNG)). The plugin allows you to configure various properties that cannot be set at runtime and require building a new app binary to take effect. If your app does not use CNG, then you'll need to manually configure the library.

Example app.json with config plugin

以下示例展示了一个配置,该配置允许在 Android 和 iOS 上共享一张或多张图片:

🌐 The following example shows a configuration that allows sharing a single or multiple images on Android and iOS:

app.json
{ "expo": { "plugins": [ [ "expo-sharing", { "ios": { "enabled": true, "activationRule": { "supportsImageWithMaxCount": 5 } }, "android": { "enabled": true, "singleShareMimeTypes": ["image/*"], "multipleShareMimeTypes": ["image/*"] } } ] ] } }

Configurable properties

NameDefaultDescription
ios.enabledfalse

A boolean value to enable the iOS Share Extension. If true, a share extension target is added to the project.

ios.extensionBundleIdentifier{appBundleIdentifier}.ShareExtension

The bundle identifier for the iOS Share Extension.

ios.appGroupIdgroup.{appBundleIdentifier}

The App Group ID to use for sharing data between the app and the extension.

ios.activationRule{}

Configuration for the NSExtensionActivationRule in Info.plist. Can be either an object confirming to the ActivationRuleOptions type to generate a standard predicate or a raw string to specify a custom predicate directly (for example, SUBQUERY(...)).

android.enabledfalse

A boolean value to enable Android share intent handling. If true, adds the necessary intent-filter to the AndroidManifest.xml.

android.singleShareMimeTypes[]

An array of MIME types to accept for single file sharing (using ACTION_SEND intent).

android.multipleShareMimeTypes[]

An array of MIME types to accept for multiple file sharing (using ACTION_SEND_MULTIPLE intent).

从其他应用共享到你的应用

🌐 Sharing to your app from other apps

重要 注意:此功能目前处于实验阶段。在 iOS 上,共享扩展则会打开主目标,而不是在共享 ViewController 中处理分享,这在苹果官方并不支持,并且在未来的 iOS 版本中可能会停止工作。

当应用用户与你的应用共享内容时,操作系统会启动你的应用(也称为将应用调到前台的过程)。要处理此操作,你需要配置导航以处理传入的深度链接。

🌐 When an app user shares content with your app, the operating system launches your app (also known as the process of bringing it to the foreground). To process this action, you need to configure your navigation to handle the incoming deep link.

Expo 路由

🌐 Expo Router

如果你正在使用 Expo Router,你可以使用 +native-intent.ts 文件来处理传入的共享意图。这允许你检查传入的路径并重定向到特定路由。

🌐 If you are using Expo Router, you can use the +native-intent.ts file to handle the incoming share intent. This allows you to inspect the incoming path and redirect to a specific route.

app/+native-intent.ts
import { getSharedPayloads } from 'expo-sharing'; export async function redirectSystemPath({ path, initial }: { path: string; initial: boolean }) { try { // Check if the URL is from the share extension/intent if (new URL(path).hostname === 'expo-sharing') { return '/handle-share'; } return path; } catch { // Fallback to the root path on error return '/'; } }

React 导航

🌐 React Navigation

如果你正在使用 React Navigation,你可以使用 linking 属性来拦截深度链接。你应该检查传入的 URL 主机名是否与 expo-sharing 方案匹配,并将用户重定向到特定的处理屏幕。

🌐 If you are using React Navigation, you can use the linking prop to intercept the deep link. You should check if the incoming URL hostname matches the expo-sharing scheme and redirect the user to a specific handler screen.

import * as Linking from 'expo-linking'; import { createStaticNavigation } from '@react-navigation/native'; import { createNativeStackNavigator } from '@react-navigation/native-stack'; const RootStack = createNativeStackNavigator({ screens: { // Other screens HandleShare: { screen: HandleShare, linking: { path: '/handle-share', }, }, }, }); const Navigation = createStaticNavigation(RootStack); function processUrl(url: string | null) { if (!url) return null; // The path to your share handler screen const handlerUrl = Linking.createURL('/handle-share'); // Check if the URL is from the share extension/intent if (new URL(url).hostname === 'expo-sharing') { return handlerUrl; } return url; } export default function App() { return ( <Navigation // The rest of your navigation config linking={{ prefixes: [Linking.createURL('/')], async getInitialURL() { const initialUrl = await Linking.getInitialURL(); return processUrl(initialUrl); }, subscribe(listener) { const linkingSubscription = Linking.addEventListener('url', ({ url }) => { const processedUrl = processUrl(url) ?? url; listener(processedUrl); }); return () => { linkingSubscription.remove(); }; }, }} /> ); }

没有导航库

🌐 No navigation library

如果你正在创建一个没有导航库的基础应用,你的主屏幕就是处理屏幕。你可以继续下一部分。

🌐 If you are creating a basic app without a navigation library, your main screen is the handler screen. You can move on to the next section.

显示共享内容

🌐 Displaying shared content

一旦你将用户重定向到处理程序屏幕,就可以使用 useIncomingShare 钩子来访问和显示共享数据。

🌐 Once you have redirected the user to a handler screen, you can use the useIncomingShare hook to access and display the shared data.

以下示例显示了一个显示共享图片的屏幕:

🌐 The following example shows a screen that displays shared images:

import { Image } from 'expo-image'; import { useIncomingShare } from 'expo-sharing'; import { View, StyleSheet, ActivityIndicator } from 'react-native'; export default function ShareReceived() { const { resolvedSharedPayloads, isResolving } = useIncomingShare(); if (isResolving) { return ( <View style={styles.container}> <ActivityIndicator size="large" /> </View> ); } return ( <View style={styles.container}> {resolvedSharedPayloads.map((payload, index) => { if (payload.contentType === 'image') { return <Image source={{ uri: payload.contentUri }} style={styles.image} key={index} />; } return null; })} </View> ); } const styles = StyleSheet.create({ container: { flex: 1, alignItems: 'center', justifyContent: 'center', backgroundColor: 'white', }, image: { width: 300, height: 300, marginBottom: 20, borderRadius: 10, }, });

应用接口

🌐 API

import * as Sharing from 'expo-sharing';

Hooks

useIncomingShare()

Android
iOS
Web

Hook, which returns the data shared with the application and updates the data if the shared payload has changed.

Methods

Sharing.clearSharedPayloads()

Android
iOS
Web

Clears the data shared with the app.

Returns:
void

Sharing.getResolvedSharedPayloadsAsync()

Experimental
 • 
Android
iOS

Returns resolved data shared with the app. Compared to data returned from getSharedPayloads contains additional information useful for reading and displaying the data. For example, when a web URL is shared with the app, a resolved payload will contain additional information about the URL contents.

Depending on what has been shared, this method may require a network connection to resolve content details.

Returns:
Promise<ResolvedSharePayload[]>

Sharing.getSharedPayloads()

Experimental
 • 
Android
iOS

Returns raw data shared with the app. Returns an empty array if no data has been shared with the app.

Returns:
SharePayload[]

Sharing.isAvailableAsync()

Android
iOS
Web

Determine if the sharing API can be used in this app.

Returns:
Promise<boolean>

A promise that fulfills with true if the sharing API can be used, and false otherwise.

Sharing.shareAsync(url, options)

Android
iOS
Web
ParameterTypeDescription
urlstring

Local file URL to share.

options(optional)SharingOptions

A map of share options.

Default:{}

Opens action sheet to share file to different applications which can handle this type of file.

Returns:
Promise<void>

Types

ActivationRuleOptions

iOS

Describes a configuration for data types that are possible to share in the application on iOS.

PropertyTypeDescription
supportsAttachmentsWithMaxCount(optional)number

Determines a maximum number of attachments that can be shared with the app. When 0 the app will not accept attachment shares.

Default:0
supportsFileWithMaxCount(optional)number

Determines a maximum number of files that can be shared with the app. When 0 the app will not accept file shares.

Default:0
supportsImageWithMaxCount(optional)number

Determines a maximum number of images that can be shared with the app. When 0 the app will not accept shared images.

Default:0
supportsMovieWithMaxCount(optional)number

Determines a maximum number of videos that can be shared with the app. When 0 the app will not accept video shares.

Default:0
supportsText(optional)boolean

Whether the app should accept shared text.

Default:false
supportsWebPageWithMaxCount(optional)number

Determines a maximum number of webpages that can be shared with the app. When 0 the app will not accept webpage shares.

Default:0
supportsWebUrlWithMaxCount(optional)number

Determines a maximum number of web URLs that can be shared with the app. When 0 the app will not accept web URL shares.

Default:0

BaseResolvedSharePayload

Android
iOS
Web

Type: SharePayload extended by:

PropertyTypeDescription
contentMimeTypestring | null

Mime type of the content accessible via the contentUri.

contentSizenumber | null

Size of the content accessible via the contentUri.

contentTypeContentType | null

Type of the content accessible via the contentUri.

contentUristring | null

URI which can be used to access the shared content. When resolving contents of a URL with redirects, contains the redirect target URI. Null when resolving a SharePayload with a text ShareType.

originalNamestring | null

If applicable, value of the suggestedFilename HTTP header field, otherwise the last path component of the contentUri field.

ContentType

Experimental
 • 
Android
iOS

Literal Type: string

Describes the resolved content type.

Acceptable values are: 'text' | 'audio' | 'image' | 'video' | 'file' | 'website'

ResolvedSharePayload

Experimental
 • 
Android
iOS

Literal Type: union

Represents a payload shared with the app, with additional information about the shared contents.

Acceptable values are: UriBasedResolvedSharePayload | TextBasedResolvedSharePayload

SharePayload

Experimental
 • 
Android
iOS

Represents raw data shared with the app.

PropertyTypeDescription
mimeType(optional)string

The MIME type of the contents of thevalue field.

Default:'text/plain'
shareType(optional)ShareType

The type of the shared content.

Default:'text'
value(optional)string

The primary value of the content.

  • For text, this is the message body.
  • For url, this is the URL string.
  • For file, image, video, or audio, this is typically the file URI.
Default:""

ShareType

Experimental
 • 
Android
iOS

Literal Type: string

Determines the type of content being shared.

  • text: Plain text content.
  • url: A specific URL.
  • audio: An audio file.
  • image: An image file.
  • video: A video file.
  • file: A generic file.

Acceptable values are: 'text' | 'url' | 'audio' | 'image' | 'video' | 'file'

SharingOptions

Android
iOS
Web
PropertyTypeDescription
anchor(optional){ height: number, width: number, x: number, y: number }
Only for:
iOS

Sets the anchor point for iPad

dialogTitle(optional)string
Only for:
Android
Web

Sets share dialog title.

mimeType(optional)string
Only for:
Android

Sets mimeType for Intent.

UTI(optional)string
Only for:
iOS

Uniform Type Identifier

  • the type of the target file.

TextBasedResolvedSharePayload

Experimental
 • 
Android
iOS

Represents a resolved payload, where a text was shared with the app.

Type: BaseResolvedSharePayload extended by:

PropertyTypeDescription
contentType(optional)'text'
-

UriBasedResolvedSharePayload

Experimental
 • 
Android
iOS

Represents a resolved payload, for which the data can be accessed through a URI.

Type: BaseResolvedSharePayload extended by:

PropertyTypeDescription
contentType'audio' | 'file' | 'video' | 'image' | 'website'
-
contentUristring
-

UseIncomingShareResult

Experimental
 • 
Android
iOS

Object returned by useIncomingShare hook containing information about data shared with the app.

PropertyTypeDescription
clearSharedPayloads() => void

Clears payloads shared with the app.

errorError | null

Contains an error encountered while resolving the shared payload. Null on success.

isResolvingboolean

Boolean indicating whether the current shared payloads are being resolved.

refreshSharePayloads() => void

Forces a refresh of the shared payloads.

resolvedSharedPayloadsResolvedSharePayload[]

Contains an array of resolved payloads shared with the app. Returns an empty array if the shared payloads are being resolved or if the resolving has failed.

sharedPayloadsSharePayload[]

Returns unresolved payloads shared with the app. Synchronous and available immediately after creating the hook.