@datalyr/react-native/CHANGELOG.md

Datalyr SDK for React Native & Expo - Server-side attribution tracking

# Changelog

All notable changes to the Datalyr React Native SDK will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.11] - 2025-06-23

### Fixed
- **Race Condition Fix**: Resolved initialization race condition where install event was tracked before SDK was fully initialized
- **Error Elimination**: Fixed "SDK not initialized. Call initialize() first" error during app install tracking
- **Improved Reliability**: SDK now properly sets initialized state before tracking any events

## [1.0.10] - 2025-06-23

### Fixed
- **Event Name Consistency**: Fixed screen view events to use `pageview` (singular) instead of `pageviews` (plural) to match web script
- **Cross-Platform Alignment**: Both React Native SDK and web script now use identical event names

## [1.0.9] - 2025-06-23

### Fixed
- **Authentication Issue Resolved**: Fixed "Invalid JWT" errors by identifying that Supabase Edge Function had JWT verification enabled
- **Correct Endpoint**: Confirmed React Native SDK uses correct Cloudflare Worker endpoint (`https://datalyr-ingest.datalyr-ingest.workers.dev`)
- **Architecture Alignment**: Both web script and React Native SDK now use the same authentication flow: SDK → Cloudflare Worker → Supabase Edge Function

### Technical Details
- Root cause was Supabase Edge Function JWT setting, not SDK authentication logic
- SDK correctly sends `Authorization: Bearer {apiKey}` header
- Cloudflare Worker acts as transparent proxy to Supabase
- Supabase Edge Function now uses custom API key validation instead of JWT verification

## [1.0.8] - 2025-06-23

### 🔧 ENDPOINT FIX - Resolves 401 Authentication Errors

#### Changed
- **Endpoint Update**: Changed default endpoint from `https://datalyr-ingest.datalyr-ingest.workers.dev` to `https://app.datalyr.com/api/ingest`
- **Web Script Alignment**: SDK now uses the same endpoint as the web tracking script for consistency

#### Fixed
- **401 Unauthorized Errors**: Resolves authentication issues by using the correct production endpoint
- **Infrastructure Alignment**: Mobile SDK now matches web infrastructure setup

#### Technical Details
- No breaking changes to the API
- Existing API keys continue to work
- Automatic retry logic remains unchanged
- All other functionality preserved

---

## [1.0.7] - 2025-06-23

### 🔄 Changed
- **BREAKING**: Changed automatic screen tracking event name from `screen_view` to `pageviews` for consistency with web analytics
- Updated session tracking to report `pageviews` instead of `screen_views` in session end events
- Updated session property names: `screen_views_in_session` → `pageviews_in_session`

### 🐛 Fixed  
- Fixed session end event payload structure
- Improved session duration calculations

---

## [1.0.6] - 2025-06-23

### 🔑 CRITICAL FIX - API Authentication Added

**BREAKING CHANGE**: API key is now required for authentication.

#### Added
- **API Key Authentication**: Added required `apiKey` field to `DatalyrConfig`
- **HTTP Authorization**: SDK now sends `Authorization: Bearer {apiKey}` header
- **401 Error Fix**: Resolves authentication errors with Datalyr API endpoints

#### Changed
- **DatalyrConfig Interface**: Added required `apiKey: string` field
- **HttpClient**: Updated to include API key in request headers
- **SDK Initialization**: Now validates both `workspaceId` and `apiKey`

#### Migration Guide
Update your SDK initialization to include the API key:

```typescript
// OLD (v1.0.5 and earlier)
await datalyr.initialize({
  workspaceId: 'your-workspace-id'
});

// NEW (v1.0.6+) - API key required
await datalyr.initialize({
  workspaceId: 'your-workspace-id',
  apiKey: 'dk_your_api_key'  // Get from Datalyr dashboard
});
```

**Where to find your API key:**
- Check your web tracking script tag
- Look for `data-api-key="dk_..."` attribute
- Contact support if you need help locating it

#### Technical Details
- API keys follow format: `dk_` + random string
- Keys are safe to include in client-side code (write-only permissions)
- Similar to Google Analytics tracking IDs or Mixpanel project tokens

---

## [1.0.5] - 2025-01-23

### 🔄 Changed
- **BREAKING**: Changed automatic screen tracking event name from `screen_view` to `pageviews` for consistency with web analytics
- Updated session tracking to report `pageviews` instead of `screen_views` in session end events
- Updated session property names: `screen_views_in_session` → `pageviews_in_session`

### 🐛 Fixed  
- Fixed SDK export pattern to use singleton instance instead of class constructor
- Resolved white screen issues caused by incorrect import/export patterns
- Fixed TypeScript compilation errors in example files

### 📚 Documentation
- Updated all documentation to reflect `pageviews` instead of `screen_view`
- Updated README.md, INSTALL.md, and EXPO_INSTALL.md
- Updated SDK_COMPLETION_STATUS.md to show correct event names
- Updated example files to use correct singleton import pattern
- Updated example UI text to show "Pageview" instead of "Screen View"

### 🔧 Technical Details
- Auto-events manager now tracks `pageviews` events for screen navigation
- Main SDK `screen()` method now tracks `pageviews` events
- Maintains backward compatibility for session tracking (still counts as `screenViews` internally)
- Fixed import pattern: `import { datalyr } from '@datalyr/react-native-sdk'`

### 🎯 Impact
- **Web Analytics Consistency**: Mobile screen tracking now uses the same event name (`pageviews`) as web page tracking
- **Improved Developer Experience**: Fixed white screen issues and import errors
- **Better Analytics**: Unified event naming makes cross-platform analytics easier

---

## [1.0.2] - Previous Release

### ✨ Features
- Automatic event tracking (sessions, screen views, app lifecycle)
- Mobile attribution tracking
- React Native and Expo support
- TypeScript support
- Automatic session management
- App install detection
- Performance tracking

### 🔧 Technical
- Event queueing and batching
- Offline support
- Retry mechanisms
- Debug logging
- Storage persistence