@nadohq/mobile-client 0.64.0 → 0.66.0

package/README.md

@@ -48,7 +48,13 @@ await mobile.setUsername({
 
 `getAvatarPresets`, `getUsernameAvailability`, `getProfiles`, `searchProfiles`, `getFollowers`, `getFollowing`, `getFeed`,
 `getNotificationPreferences`, `getRegisteredWallet`, `getForYouFeed`, `getTopTradersFeed`,
-`getFriendsFeed`, `getProfileFeed`, `getMarketFeed`, `getPositionFeed`, `getFeedItem`, `getFeedUpdates`.
+`getFriendsFeed`, `getProfileFeed`, `getMarketFeed`, `getPositionFeed`, `getFeedItem`, `getFeedUpdates`,
+`getSelfFeedPositions`, `resolveFeedPosition`, `resolveFeedAction`, `getFeedChartDrawing`, `getFeedComments`,
+`getPositionHistory`, `getPositionChart`, `getPositionWatchers`.
+
+`getNotificationRegistrationV2` and `getNotificationSettingsV2` use an active Expo token as their credential,
+not a wallet signature. Before displaying wallet settings, compare the wallet returned by `getRegisteredWallet`
+with the connected wallet (case-insensitively).
 
 `getProfiles` is the only profile route: it batches up to 25 subaccounts, returns them in the requested order,
 and carries follower totals (`include.followCounts`) and a follow summary (`include.followSummary.viewAs`) as
@@ -68,19 +74,130 @@ page is ordered by the listed relationship alone and `isFollowing` is absent rat
 
 `getFeed` returns the global trade feed. Session-based feeds include `getForYouFeed`, `getTopTradersFeed`,
 and `getFriendsFeed` (requires `viewAs`), plus `getProfileFeed`, `getMarketFeed`, and `getPositionFeed`.
-`getFeedItem` reads one item; `getFeedUpdates` polls session patches using the returned `viewerToken`.
-All are unsigned. Profile, position, and item reads include the `viewAs` account's own hidden content under
-`account_view`; the viewing account is not proof of wallet ownership. Prices are decimal `BigNumber` values;
-quantities, notionals, and PnL retain x18 units. See method and parameter JSDoc for session and polling rules.
+`getFeedItem` reads one item; pass `viewEventId` when the user navigates into the detail so a later
+`recordFeedViews` can count that visit, and omit it for prefetch. `getFeedUpdates` polls session patches
+using the returned `viewerToken`. All are unsigned. Profile, position, and item reads include the `viewAs`
+account's own hidden content under `account_view`; the viewing account is not proof of wallet ownership.
+Prices are decimal `BigNumber` values; quantities, notionals, and PnL retain x18 units. See method and
+parameter JSDoc for session and polling rules.
+
+`getSelfFeedPositions`, `resolveFeedPosition`, and `resolveFeedAction` require `viewAs` and return eligibility
+hints for that account, not authenticated permissions. `getFeedComments` supports anchored, bidirectional
+thread pagination. Lists, details, and history return parsed drawings and readable comment previews;
+`getFeedChartDrawing` refreshes a drawing independently when needed.
+
+`getPositionHistory` returns the full action/take timeline, distinct from published-only `getPositionFeed`,
+and a position-mode session for navigation and updates. `getPositionChart` returns candles and action markers,
+keeping execution and liquidation Oracle prices separate. `getPositionWatchers` reads visitor counts without
+registering presence. Watching account previews are self-reported, not proof of account ownership.
 
 ### Public Executes
 
-`unregisterExpoToken`, `updateNotificationPreferences`. These are authenticated by possession of an active Expo
+`unregisterExpoToken`, `updateNotificationPreferences`, `updateNotificationSettingsV2`. These are authenticated by possession of an active Expo
 push token rather than a wallet signature, so they still work at logout when a signature may be unobtainable.
 
+`recordFeedViews` and `setPositionPresence` use reading-session credentials rather than wallet signatures.
+Exposure follows `readSession.viewTracking.mode === 'detail_visit'`: after the primary detail target is shown
+in the foreground, call `recordFeedViews` with the same `viewEventId` previously sent to `getFeedItem`, plus
+that response's `sessionId` / `viewerToken` and exactly one detail-target `itemId`. Reuse the event on retries
+for the same visit; generate a new UUID only after leaving and re-entering. Fetch image bytes with
+`getFeedImageBytes` using the same session credentials and paths from `images` / `thumbnail.url`. Legitimate
+session reads renew the idle expiration; use the latest `expiresAtMs` rather than treating the first value as
+fixed.
+
+For React Native `Image` or expo-image, use `getFeedImageRequest` to pass the authenticated
+URL and headers directly without converting bytes to base64:
+
+```ts
+const { url, headers } = mobile.getFeedImageRequest({
+  path: image.url,
+  sessionId: readSession.sessionId,
+  viewerToken: readSession.viewerToken,
+});
+const source = { uri: url, headers };
+```
+
 ### Signed Executes
 
-`setUsername`, `setBio`, `createAvatarUpload`, `setAvatar`, `setPrivateMode`, `registerExpoToken`, `setFollow`.
+`setUsername`, `setBio`, `createAvatarUpload`, `setAvatar`, `setPrivateMode`, `registerExpoToken`, `setFollow`,
+`createFeedPost`, `createFeedComment`, `createFeedPostImageUpload`, `createFeedCommentImageUpload`,
+`createFeedChartDrawing`, `updateFeedChartDrawing`, `setFeedLike`, `registerExpoTokenV2`,
+`updateNotificationSubscriptions`, `recordProductEvents`.
+
+Upload images one at a time with the multipart helpers (≤ 2 MiB whole request), then pass ordered ready
+`imageIds` to `createFeedPost` / `createFeedComment`. The SDK throws `RangeError` before requesting a signature or sending a request
+that exceeds `MOBILE_FEED_IMAGE_MAX_REQUEST_BYTES`, including the signed payload and multipart framing.
+Unconfigured image storage returns `SOCIAL_FEED_DATA_UNAVAILABLE` (6320, HTTP 503).
+Posts still require nonblank text or a drawing; comments
+still require nonblank text. See method and parameter JSDoc for publication, retries, mention offsets, drawing
+data, and mutation ordering.
+
+### Signed Queries
+
+`getNotificationSubscriptions` and `getNotificationInboxV2` use wallet authentication on `/query`.
+They do not require an Expo token or system push permission. The configured linked signer is supported.
+
+### Notifications V2
+
+The notification v2 operations are available on `MobileClient`, including `client.context.mobileClient` from
+`@nadohq/client`. Settings, capabilities, subscriptions, inbox data, and product events use camelCase SDK models.
+The SDK maps requests to snake_case wire fields and removes the success envelope from read results.
+
+```ts
+const auth = {
+  subaccountOwner: walletClient.account.address,
+  subaccountName: 'default',
+  chainId: ink.id,
+  verifyingAddr: '0x...' as const,
+};
+
+await mobile.registerExpoTokenV2({
+  ...auth,
+  expoToken,
+  platform: 'ios',
+  capabilities: {
+    payloadVersions: [2],
+    typeIds: ['order_fill', 'new_follower'],
+    routes: ['portfolio', 'profile'],
+  },
+});
+const registration = await mobile.getNotificationRegistrationV2({ expoToken });
+const current = await mobile.getNotificationSettingsV2({ expoToken });
+const saved = await mobile.updateNotificationSettingsV2({
+  expoToken,
+  expectedRevision: current.revision,
+  settings: { ...current.settings, positionThresholds: [25] },
+});
+
+const subscriptions = await mobile.getNotificationSubscriptions(auth);
+await mobile.updateNotificationSubscriptions({
+  ...auth,
+  update: {
+    expectedRevision: subscriptions.revision,
+    market: { productId: 2, subscribed: true },
+  },
+});
+const updatedSubscriptions = await mobile.getNotificationSubscriptions(auth);
+const inbox = await mobile.getNotificationInboxV2({ ...auth, limit: 20 });
+```
+
+- Declare only types/routes the application handles. Re-registration advances the generation and cancels
+  old pending deliveries; calling legacy `registerExpoToken` resets capabilities to v1.
+- Settings replacement requires every field. Settings and subscription revisions are independent.
+  On `MOBILE_ERROR_CODES.NOTIFICATION_REVISION_CONFLICT` (6203), re-read and merge only the current user change.
+- A subscription update selects exactly one operation; omit the other operations and the SDK sends them as `null`. Successful subscription
+  updates return only status, so re-query even after repeated ON/OFF. Favorites import merges once, never replaces.
+- Enabling a bell requires following the target. Unfollowing clears its bell without advancing the subscription
+  revision; refresh subscriptions after follow mutations. Bells are Identity-scoped; markets are wallet-scoped.
+  Pass `traderBell.subaccount` as a `Subaccount` (`subaccountOwner` and `subaccountName`); the SDK encodes it for signing.
+- Inbox pages are accepted intents, not delivery/read receipts. There is no title/body, unread count, mark-read,
+  or delete operation. Do not use the unimplemented legacy `notification_history` route.
+  An unknown destination rejects the page with `MobileUnsupportedNotificationRouteError`.
+- `recordProductEvents({ ...auth, events })` accepts 1-50 events atomically. Provide the fields required by `eventName`,
+  actual millisecond timestamps, and stable `clientEventId` UUIDs across retries. The SDK fills unused wire fields with `null`. Supported
+  names are `notif_opened`, `market_viewed`, `chart_opened`, and `search`; obtain analytics consent first.
+- Legacy preferences remain supported and synchronize overlapping v2 fields. Keep legacy push parsing because
+  order notifications may use a v1 fallback even for v2 registrations.
 
 ### Linked Signers