> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/pushly-ja/integration/implementation-steps/react-native-expopuraguin/expopuraguin.md).

# Expoプラグイン変更履歴

Expoプラグインの更新一覧

{% updates format="full" %}
{% update date="2026-08-19" %}

## 1.4.0

**更新**

* 〜を狭めます `@pushly/push-sdk-react-native` peer dependency を 1.8 系（`>=1.8.0 <1.9.0`）にし、iOS pod の下限もそれに合わせて引き上げます。以前のプラグイン版を使っている利用者はアップグレードが必要です。バージョンを混在させると解決時に失敗します。
  {% endupdate %}

{% update date="2026-07-30" %}

## 1.3.0

**更新**

* 〜を拡大します `@pushly/push-sdk-react-native` peer dependency を拡張し、1.7 SDK 系をサポートします。以前のプラグイン版を使っている利用者はアップグレードが必要です。
  {% endupdate %}

{% update date="2026-04-14" %}

## 1.1.2

* iOS pod を〜に更新 `~> 1.6.1`
* 修正: 同じ通知コールバックをフックする別のライブラリと併用して iOS の method swizzling を有効にした場合に発生していた競合状態のクラッシュを解決しました。
  {% endupdate %}

{% update date="2026-04-02" %}

## 1.1.1

* パッケージの役割を明確化: `@pushly/push-sdk-expo` (Expo 設定プラグイン) 対 `@pushly/push-sdk-react-native` (ランタイム SDK)
* iOS 連携を改善:
  * アプリと Notification Service Extension 間でデプロイメントターゲットを自動的に同期します。
  * Pushly の iOS pod を〜に更新 `~> 1.6.0` し、一般的な Xcode の署名問題を軽減します。
* Android 連携を改善:
  * デフォルトの Firebase Messaging 通知チャンネルを確実に設定します。
    {% endupdate %}

{% update date="2026-02-24" %}

## 1.0.0

* Expo prebuild/EAS Build とカスタム開発クライアントをサポートする初回リリース
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/pushly-ja/integration/implementation-steps/react-native-expopuraguin/expopuraguin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.