@traffical/react-native 0.8.2 → 0.8.4

package/README.md

@@ -29,7 +29,8 @@ function App() {
         orgId: 'org_123',
         projectId: 'proj_456',
         env: 'production',
-        apiKey: 'pk_...',
+        apiKey: 'traffical_pk_…',
+        evaluationMode: 'bundle', // required with a publishable key — see below
       }}
       loadingComponent={<ActivityIndicator size="large" />}
     >
@@ -39,6 +40,20 @@ function App() {
 }
 ```
 
+> **Publishable keys need `evaluationMode: 'bundle'`.**
+>
+> This package defaults to `evaluationMode: 'server'`, which calls `/v1/resolve`.
+> That endpoint rejects publishable (`traffical_pk_…`) keys, so leaving the
+> default in place with a `pk` returns `403` on every resolution.
+>
+> Set `evaluationMode: 'bundle'` and the SDK fetches the config bundle once and
+> resolves on-device — no per-decision network call, works offline, and it is the
+> mode we recommend for mobile regardless of key type.
+>
+> If you specifically need server-evaluated mode, it requires a server-side SDK
+> key (`traffical_sk_…`), which must not ship in a mobile binary. In practice that
+> means proxying resolution through your own backend.
+
 ### 2. Use the `useTraffical` hook in your screens
 
 ```tsx
@@ -98,7 +113,7 @@ Initializes the Traffical client with React Native defaults and provides it to c
 | `config.env` | `string` | Yes | Environment (e.g., "production", "staging") |
 | `config.apiKey` | `string` | Yes | API key for authentication |
 | `config.baseUrl` | `string` | No | Base URL for the control plane API |
-| `config.evaluationMode` | `"server" \| "bundle"` | No | Resolution mode (default: `"server"`) |
+| `config.evaluationMode` | `"server" \| "bundle"` | No | Resolution mode (default: `"server"`). Use `"bundle"` with a publishable key — `"server"` calls `/v1/resolve`, which rejects `traffical_pk_…` keys |
 | `config.refreshIntervalMs` | `number` | No | Background refresh interval (default: 60000) |
 | `config.unitKeyFn` | `() => string` | No | Function to get the unit key. If not provided, uses automatic stable ID |
 | `config.contextFn` | `() => Context` | No | Function to get additional context |
@@ -398,10 +413,10 @@ function PaywallScreen() {
 
 ### 1. Always Provide Sensible Defaults
 
-Defaults are used when no experiment is running, the user doesn't match targeting, or the SDK is still loading.
+Defaults are used when no policy is running, the user doesn't match targeting, or the SDK is still loading.
 
 ```tsx
-// ✅ Good: works without any experiment
+// ✅ Good: works without any policy
 const { params } = useTraffical({
   defaults: {
     'pricing.discount': 0,
@@ -448,7 +463,7 @@ category.subcategory.name
 
 feature.*     → Feature flags        (boolean)
 ui.*          → Visual variations    (string, number)
-pricing.*     → Pricing experiments  (number)
+pricing.*     → Pricing policies     (number)
 copy.*        → Copywriting tests    (string)
 onboarding.*  → Onboarding flow      (mixed)
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@traffical/react-native",
-  "version": "0.8.2",
+  "version": "0.8.4",
   "description": "Traffical SDK for React Native - server-evaluated feature flags, A/B testing, and adaptive optimization",
   "type": "module",
   "main": "./dist/index.js",
@@ -22,8 +22,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@traffical/core": "0.11.1",
-    "@traffical/js-client": "0.16.2"
+    "@traffical/core": "0.12.0",
+    "@traffical/js-client": "0.18.0"
   },
   "devDependencies": {
     "@types/bun": "latest",