 hailin
|
3bc35bad64
|
feat(push): add offline push notification system (FCM + HMS + Mi + OPPO + vivo)
## Backend (notification-service)
- Add `device_push_tokens` table (migration 014) — stores per-user tokens per
platform (FCM/HMS/MI/OPPO/VIVO) with UNIQUE constraint on (user_id, platform, device_id)
- Add `DevicePushTokenRepository` with upsert/delete/targeting queries
(by userId, tenantId, plan, tags, segment)
- Add push provider interface with `sendBatch(tokens, message): BatchSendResult`
returning `invalidTokens[]` for automatic DB cleanup
- Add FCM provider — OAuth2 via RS256 JWT, chunked concurrency (max 20 parallel),
detects UNREGISTERED/404 as invalid tokens
- Add HMS provider — native batch API (1000 tokens/chunk), OAuth2 token cache
with 5-min buffer, detects code 80100016
- Add Xiaomi provider — `/v3/message/regids` batch endpoint (1000/chunk),
parses `bad_regids` field
- Add OPPO provider — single-send with Promise-based mutex to prevent concurrent
auth token refresh races
- Add vivo provider — `/message/pushToList` batch endpoint, mutex same as OPPO,
parses `invalidMap`
- Add `OfflinePushService` — groups tokens by platform, sends concurrently,
auto-deletes invalid tokens; fire-and-forget trigger after notification creation
- Add `DevicePushTokenController` — POST/DELETE `/api/v1/notifications/device-token`
- Wire offline push into `NotificationAdminController` and `EventTriggerService`
- Add Kong route for device-token endpoint (JWT required)
- Add all push provider env vars to docker-compose notification-service
## Flutter (it0_app)
- Add `PushService` singleton — detects OEM (Huawei/Xiaomi/OPPO/vivo/FCM),
initialises correct push SDK, registers token with backend
- FCM: full init with background handler, foreground local notifications,
tap stream, iOS APNs support
- HMS: `HuaweiPush` async token via `onTokenEvent`, no FCM fallback on failure
(Huawei without GMS cannot use FCM)
- Mi/OPPO/vivo: MethodChannel bridge to Kotlin receivers; handler set before
`getToken()` call to avoid race
- `_initialized` guard prevents double-init on hot-restart
- `static Stream<void> onNotificationTap` for router navigation
- Add Kotlin OEM bridge classes: `MiPushReceiver`, `OppoPushService`,
`VivoPushReceiver` — forward token/message/tap events to Flutter via MethodChannel
- Update `MainActivity` — register all three OEM MethodChannels; OEM credentials
injected from `BuildConfig` (read from `local.properties` at build time)
- Update `build.gradle.kts` — add Google Services + HMS AgConnect plugins,
BuildConfig fields for OEM credentials, `fileTree("libs")` for OEM AARs
- Update `android/build.gradle.kts` — add buildscript classpath for GMS + HMS,
Huawei Maven repo
- Update `AndroidManifest.xml` — HMS service, Xiaomi receiver + services,
vivo receiver; OPPO handled via AAR manifest merge
- Add OEM SDK AARs to `android/app/libs/`:
MiPush 7.9.2, HeytapPush 3.7.1, vivo Push 4.1.3
- Add `google-services.json` (Firebase project: it0-iagent, package: com.iagent.it0_app)
- Add `firebase_core ^3.6.0`, `firebase_messaging ^15.1.3`, `huawei_push ^6.11.0+300`
to pubspec.yaml
- Add `ApiEndpoints.notificationDeviceToken` endpoint constant
## Ops
- Add FCM_PROJECT_ID, FCM_CLIENT_EMAIL, FCM_PRIVATE_KEY (+ HMS/Mi/OPPO/vivo placeholders)
to `.env.example` with comments pointing to each OEM's developer portal
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
2026-03-10 02:42:34 -07:00 |