(2023/2/10 13:21 JST) APK updated.
- (noFCM variant) remove kotlinx-coroutines-play-services.
- improve showing avatar icons. APNG support. rounded corner for animation icon.
(2023/2/10 1:33 JST) APK updated.
- (FCM variant) check Play developer services are available on the device.
- (FCM variant) when onNewToken() called, start updating the push delivery endpoint.
- if push delivery service not available, show warning and guide about installing UnifiedPush compatible push distributor app.
(2023/2/9 15:22 JST) APK updated.
Fix minor issues.
- the push subscription update worker was started every time return from the child screen.
- reduce load of cases that an account not require pull notification check.
- reduce in-app DB update when update notification status.
- reduce adb log output.
(2023/2/9 9:11 JST) APK updated.
- Fix access token update is not correctly saved.
(2023/2/9 6:36 JST) APK updated.
- Fix about importing app data.
- Add automatic upgrade push subscription from old style push subscription.
Early test
This release is an early test of the revamped push notification support. It can be extremely unstable. We strongly recommend exporting and saving your app data before updating.
このリリースは刷新されたプッシュ通知対応の早期テストです。著しく不安定な可能性があります。更新する前にアプリデータをエクスポートして保存することを強くお勧めします。
Completely rewritten app server
- Completely rewritten in Kotlin programming language.
- Supports both FCM and UnifiedPush.
- Transfer WebPush data from SNS server to the app as it is.
- All user-identifiable information for endpoint registration from the app is hashed. (Excluding push delivery destination information)
- When receiving a huge amount of data from the SNS server, it is temporarily stored and only the ID is sent to the app.
完全に書き直されたアプリサーバ
- Kotlinプログラミング言語で完全に書き直しました。
- FCMとUnifiedPushの両方をサポートします。
- SNSサーバからのWebPushデータをそのままアプリに転送します。
- アプリからのエンドポイント登録について、ユーザを特定できる情報の全てがハッシュ化されています。(プッシュ配送の宛先情報を除く)
- SNSサーバから巨大なデータを受け取った場合、それを一時的に保存してアプリにはIDだけを伝えます。
Enhanced push notification support
- No longer access the SNS server's REST API every time you receive a push notification. Users with a large number of installed devices will no longer get 429 throttling limits on their SNS servers.
- Generate your own private key for push subscription.
- Supports Unified Push. Push delivery apps such as ntfy can be used together.
- It is now possible to provide a noFCM build that does not include Google FCM.
強化されたプッシュ通知サポート
- プッシュ通知を受け取る度にSNSサーバのREST APIにもはやアクセスしません。インストール端末数が多いユーザがSNSサーバに429 スロットリング制限を受けることはもうありません。
- プッシュ購読時の秘密鍵を独自に生成します。
- Unified Push対応。ntfyなどのプッシュ配送アプリを併用することができます。
- Google FCM を含まない noFCM ビルドを提供可能になりました。
Keep old implementation
- Periodic pull notification check is turned off by default. However, it can be enabled in your account settings for customized server environments.
古い実装の維持
- 定期的なPull通知チェックはデフォルトオフになります。しかしカスタマイズされたサーバ環境のためにアカウント設定で有効にできます。
about noFcm variant
- Two variants are offered from this version. FCM(play store), noFCM.
- FCM (play store) is the same route as what we have provided so far.
- noFCM is variant of removed dependency related Google FCM to avoid user tracking by Google Firebase.
- They have different package name that recognized as different app on the device.
- then, you can't update directly from old installed FCM(play store) variant to noFCM variant.
- to move your account data and customizations, use "app settings/export app data" and "app settings/import app data".
- noFcm variant has no usage statistics provided by the Play Store, such as crash report, user/install statistics. Therefore, it is somewhat difficult to troubleshooting.