@onairos/react-native 3.6.8 → 3.6.9

package/lib/commonjs/config/webchangelog/md

@@ -0,0 +1,607 @@
+# Changelog
+
+All notable changes to the Onairos SDK will be documented in this file.
+
+## [5.8.22] - 2026-02-22
+
+### 🐛 Bug Fix - Cached Login / Session Persistence
+
+#### Problem Fixed
+- **Cached login was not working** - users were being asked to sign in again even with a valid session
+- Session data flags (`onboardingComplete`, `pinCreated`) were not being persisted after flow completion
+
+#### Root Cause
+When onboarding or PIN setup completed, if the session was already valid (not expired), only `extendSession()` was called instead of `createSession()`. The `extendSession()` function only bumps the session expiry but does NOT update the stored user data with the new flags.
+
+This caused:
+1. User completes onboarding → `onboardingComplete: true` set in memory but not persisted to session
+2. User completes PIN → `pinCreated: true` set in memory but not persisted to session
+3. User returns later → `checkValidSession()` reads old flags (both false) → session considered incomplete → login required
+
+#### Solution
+Always call `createSession()` with updated user data when flags change, not just `extendSession()`.
+
+---
+
+### ✨ Enhancement - Data Request UI Improvements
+
+#### Changes
+- **Raw Memories option visibility**: Now properly handles apps that don't request raw/LLM data
+  - If app doesn't request raw data: option shows greyed out with "Not used by this app" hover text
+  - If user has no LLM connections: option shows greyed out with "Connect an LLM app first" hover text
+- **Added descriptions under data types** (matching Connections page style):
+  - Basic Profile: "Your basic profile information"
+  - Preferences: "Your preferences towards {appName}"
+  - Interests: "Overview of your personality"
+  - Raw Memories: "Secure raw app data from your LLM connections" (or disabled reason if unavailable)
+
+---
+
+## [5.8.19] - 2026-02-22
+
+### 🐛 Critical Fix - Next.js 16 Turbopack Compatibility
+
+#### Problem Fixed
+- **Turbopack parsing errors when importing onairos in Next.js 16+ App Router:**
+  - `SyntaxError: Function statements require a function name`
+  - `ChunkLoadError: Failed to load chunk server/chunks/ssr/...onairos_esm...`
+  - `Turbopack panic: x Expected ident` / `x Expected ';', '}' or <eof>`
+- ESM bundle was incompatible with Turbopack's stricter SWC-based JavaScript parser
+- Obfuscated code patterns (IIFEs, hexadecimal identifiers, RC4 decoders) broke parsing
+
+#### Root Cause
+Turbopack uses SWC (Rust-based parser) which is stricter than Webpack's Acorn parser.
+`javascript-obfuscator` produces valid JavaScript that SWC cannot parse in certain edge cases:
+
+| Pattern | Example | SWC Error |
+|---------|---------|-----------|
+| IIFE with hex identifiers | `function(_0x1a2b){...}` | "Function statements require function name" |
+| RC4 decoder wrappers | `(function(){...})()` | Malformed IIFE detection |
+| Control flow flattening | `switch(_0x...){case...}` | "Expected ident" errors |
+| Dead code injection | Anonymous unreachable functions | Parser panics |
+
+#### Solution Implemented
+**Full obfuscation preserved with post-build normalization:**
+
+1. ESM builds use **full-strength obfuscation** (RC4, control flow flattening, etc.)
+2. After webpack completes, `scripts/normalize-esm-for-turbopack.cjs` runs the output through Babel
+3. Babel's parser/generator normalizes the AST into standard-form JavaScript
+4. The result is fully obfuscated code that Turbopack can parse
+
+**Build flow:**
+```
+Webpack → Obfuscate (full) → Babel normalize → Turbopack-compatible output
+```
+
+**No security trade-off** - ESM builds retain the same protection level as before:
+- RC4 string encryption
+- Control flow flattening
+- Dead code injection
+- Hexadecimal identifiers
+- String splitting
+- Object key transformation
+
+#### Migration
+Simply update to 5.8.19:
+```bash
+npm install onairos@5.8.19
+# or
+yarn add onairos@5.8.19
+```
+
+No code changes required - the fix is entirely in the distributed bundle.
+
+---
+
+## [4.3.6] - 2024-12-24
+
+### 🐛 Critical Fix - Google Sign-In Token Type (ID Token vs Access Token)
+
+#### Problem Fixed
+- **Backend error: "Wrong number of segments in token"**
+- SDK was sending **access token** (`ya29.xxx...`) instead of **ID token** (JWT `eyJhbGciOiJ...`)
+- Backend expects ID token (JWT with 3 segments) for authentication verification
+- Access tokens cannot be decoded/verified as JWTs
+
+#### Solution Implemented
+- **Switched from `useGoogleLogin` hook to `GoogleLogin` component**
+- `useGoogleLogin` returns access token (for API calls) ❌
+- `GoogleLogin` returns ID token (for authentication) ✅
+- Backend now receives proper JWT ID token for verification
+
+#### Technical Details
+
+**Token Format Comparison:**
+| Token Type | Format | Segments | Use Case |
+|------------|--------|----------|----------|
+| ID Token (JWT) ✅ | `eyJhbGciOiJ...` | 3 (header.payload.signature) | Authentication |
+| Access Token ❌ | `ya29.xxx...` | Variable | API calls |
+
+**Before (BROKEN):**
+```javascript
+// Using useGoogleLogin - returns access token
+const googleLogin = useGoogleLogin({
+  onSuccess: (tokenResponse) => {
+    const accessToken = tokenResponse.access_token;  // ya29.xxx
+    // Send to backend → JWT decode fails!
+  }
+});
+```
+
+**After (FIXED):**
+```javascript
+// Using GoogleLogin component - returns ID token
+<GoogleLogin
+  onSuccess={(credentialResponse) => {
+    const idToken = credentialResponse.credential;  // eyJhbGciOiJ... (JWT)
+    // Send to backend → JWT decode succeeds! ✅
+  }}
+/>
+```
+
+#### Files Changed
+- `src/components/EmailAuth.js`:
+  - Changed import: `useGoogleLogin` → `GoogleLogin`
+  - Removed custom `GoogleButton` component (no longer needed)
+  - Implemented `handleGoogleSuccess()` to handle ID token
+  - Decode JWT to extract email before sending to backend
+  - Updated comments to clarify ID token vs access token
+  - Replaced custom button with official `<GoogleLogin>` component
+
+#### Impact
+- ✅ Backend receives proper JWT ID token (3 segments)
+- ✅ JWT verification succeeds in backend
+- ✅ Google Sign-In authentication works correctly
+- ✅ Account creation succeeds
+- ✅ Platform connections work for new Google users
+
+#### Backend Integration
+- Endpoint: `POST /google/google`
+- Receives: `{ credential: "eyJhbGciOiJ..." }` (ID token, not access token)
+- Backend can now decode and verify JWT successfully
+
+---
+
+## [4.3.5] - 2024-12-24
+
+### 🐛 Critical Fix - Google Sign-In Account Creation
+
+#### Problem Fixed
+- **New Google users were NOT getting accounts created in the backend**
+- After Google Sign-In, frontend only checked if account exists but never created it
+- This caused platform connection failures: "Account doesn't exist" error when connecting YouTube
+- Backend diagnostics showed: `/getAccountInfo/email` called but NO account creation endpoint called
+
+#### Solution Implemented
+- **Added `/google/google` endpoint call** after Google Sign-In to create/login account
+- Frontend now properly authenticates with backend and receives JWT token
+- Backend creates account if it doesn't exist, or logs in existing user
+- Platform connections now succeed for new Google users
+
+#### Technical Details
+
+**Before (BROKEN):**
+```javascript
+// Google Sign-In → Get email
+// Call /getAccountInfo/email → "No Account Found"
+// ❌ No backend call to create account
+// Proceed to YouTube connection → FAILS
+```
+
+**After (FIXED):**
+```javascript
+// Google Sign-In → Get email + access token
+// Call /google/google with credential → Account created + JWT token returned
+// ✅ Account exists in backend
+// Proceed to YouTube connection → SUCCESS
+```
+
+#### Files Changed
+- `src/components/EmailAuth.js`:
+  - Updated `handleOAuthSuccess()` to call `/google/google` endpoint
+  - Pass Google access token as `credential` to backend
+  - Receive and store JWT token from backend response
+  - Updated `googleLogin` hook to pass access token to handler
+
+#### Impact
+- ✅ NEW Google users now get accounts created properly
+- ✅ Platform connections (YouTube, etc.) succeed for new users
+- ✅ JWT tokens properly issued and stored
+- ✅ Existing Google users continue to work (login flow)
+
+#### Backend Integration
+- Uses existing `/google/google` endpoint
+- Sends: `{ credential: googleAccessToken }`
+- Receives: `{ body: { token, username, isNewUser } }`
+
+For full technical analysis, see `GOOGLE_SIGNIN_ACCOUNT_CREATION_BUG.md`
+
+---
+
+## [4.2.3] - 2025-12-14
+
+### 🐛 Critical Fix - Email Authentication Routing (Corrects 4.2.2)
+
+#### Problem Fixed
+- **Version 4.2.2 introduced a bug**: NEW users via email authentication were incorrectly routed to dataRequest instead of onboarding
+- **Root cause**: Added `/getAccountInfo/email` check AFTER email verification, but backend creates account during verification
+- **Result**: Account check always found account exists (even for new users), causing wrong routing
+
+#### Solution Implemented
+- **Trust backend's `isNewUser` field** - Backend knows if account was just created during verification
+- **Removed unnecessary API call** - No longer call `/getAccountInfo/email` after email verification
+- **Consistent with backend design** - Both `/email/verify/confirm` and `/auth/google` are authoritative about user status
+
+#### Technical Details
+
+**Before (4.2.2 - BROKEN):**
+```javascript
+// Email verification creates account and returns isNewUser: true
+// Then we called /getAccountInfo/email
+// Found account exists (just created!) → treated as existing user ❌
+```
+
+**After (4.2.3 - FIXED):**
+```javascript
+// Email verification returns isNewUser: true
+// Trust this field directly → route to onboarding ✅
+```
+
+#### Files Changed
+- `src/components/EmailAuth.js`:
+  - Email verification: Trust `data.isNewUser` from verification response
+  - Google sign-in: Trust `authData.body.isNewUser` from `/auth/google` response
+  - Removed post-verification `/getAccountInfo/email` call that caused the bug
+
+#### Impact
+- ✅ NEW email users now correctly route to onboarding (FIXED)
+- ✅ EXISTING email users still correctly route to dataRequest (unchanged)
+- ✅ NEW Google users still correctly route to onboarding (unchanged)
+- ✅ EXISTING Google users still correctly route to dataRequest (unchanged)
+
+For detailed technical analysis, see `FIX_4.2.3_CORRECT_IMPLEMENTATION.md` and `AUTHENTICATION_FLOW_ANALYSIS.md`
+
+---
+
+## [4.2.2] - 2025-12-14 (SUPERSEDED BY 4.2.3)
+
+### 🐛 Fixed - Email Authentication Routing for Existing Users
+
+#### Problem Resolved
+- **Critical Bug**: Existing users authenticating via email verification were incorrectly routed to onboarding instead of dataRequest page
+- **Root Cause**: Frontend was checking non-existent `data.existingUser` field instead of `data.isNewUser` returned by backend
+- **Impact**: Existing users had to go through onboarding again instead of proceeding directly to data request
+
+#### Solution Implemented
+- Added explicit account status check via `/getAccountInfo/email` endpoint (matching Google sign-in behavior)
+- Email verification flow now fetches complete account data after code verification
+- Both Google OAuth and email authentication flows now return identical account data structures
+- Uses `accountStatus.exists` field for consistent user routing logic
+
+#### Technical Details
+**Before Fix:**
+```javascript
+// Backend returns: { isNewUser: false }
+// Frontend checked: data.existingUser (undefined)
+// Result: existingUser = false (WRONG!)
+// Route: onboarding (WRONG for existing users!)
+```
+
+**After Fix:**
+```javascript
+// Explicit account check via /getAccountInfo/email
+// Gets: { accountStatus: { exists: true } }
+// Result: existingUser = true (CORRECT!)
+// Route: dataRequest (CORRECT for existing users!)
+```
+
+#### Files Changed
+- `src/components/EmailAuth.js` - Added explicit account status check in `handleCodeSubmit()`
+- Improved logging for account status verification
+- Enhanced error handling and fallback logic
+
+#### Benefits
+- ✅ Existing users now correctly route to dataRequest page via email auth
+- ✅ Consistent behavior between Google and email authentication
+- ✅ Full account data available for both authentication flows
+- ✅ Better user experience for returning users
+- ✅ No breaking changes to existing functionality
+
+For detailed technical analysis, see `EMAIL_AUTH_CONSISTENCY_FIX.md`
+
+---
+
+## [4.0.16] - 2025-12-01
+
+### 🎉 Major Fix: Full Tailwind CSS v3 & v4 Compatibility
+
+#### Fixed
+- ✅ **RESOLVED**: Peer dependency conflict error with Tailwind CSS v3
+- ✅ Package now works with **Tailwind v3.0+ and v4.0+** without any workarounds
+- ✅ Brandon's issue with `tailwindcss@3.4.18` now resolved
+- ✅ No need for `--force` or `--legacy-peer-deps` flags
+
+#### Added
+- `INSTALLATION_GUIDE.md` - Comprehensive installation guide for both Tailwind versions
+- Automatic version compatibility detection
+- Clear upgrade path documentation for developers who want to move to v4
+
+#### Changed
+- Peer dependency: `"tailwindcss": ">=3.0.0"` (supports all v3 and v4 versions)
+- Version bumped to 4.0.16
+
+#### Developer Instructions
+**No configuration changes needed!** Just run:
+```bash
+npm install onairos@latest
+```
+
+Works automatically with:
+- Tailwind CSS v3.4.x (Brandon's version with the error)
+- Tailwind CSS v4.1.x
+- All versions >=3.0.0
+
+---
+
+## [4.0.1] - 2025-11-14
+
+### 🎯 TypeScript Enhancement: onComplete Callback
+
+#### Enhanced Type Definitions
+- **NEW**: Added comprehensive `OnairosCompleteData` interface with full type documentation
+- **IMPROVED**: Specified `token: string` and `apiUrl: string` as core response properties
+- **NEW**: Documented all optional fields with detailed comments
+- **NEW**: Added enhanced formatting fields (`userDataSummary`, `prettyPrint`)
+
+#### Bug Fixes
+- **FIXED**: Test mode now includes mock `token` field for consistent data structure
+- **FIXED**: Test mode returns identical structure to production mode
+
+#### Developer Experience
+- **NEW**: Added comprehensive logging for `onComplete` data structure validation
+- **NEW**: Visual indicators (✅/❌) for presence of key fields in console
+- **NEW**: Detailed logging shows token preview, apiUrl, and all returned keys
+- **NEW**: Created `ONCOMPLETE_USAGE_EXAMPLE.md` with complete usage documentation
+
+#### Documentation
+- **NEW**: TypeScript interface examples with proper typing
+- **NEW**: JavaScript usage examples with authentication patterns
+- **NEW**: Complete field documentation with descriptions
+- **NEW**: Test mode vs Production mode comparison
+- **NEW**: Examples of authenticated API requests using token and apiUrl
+
+#### Code Quality
+- **IMPROVED**: Better console debugging output at all stages of data flow
+- **IMPROVED**: DataRequest component logs token and apiUrl presence before callback
+- **IMPROVED**: OnairosButton logs complete data structure before passing to parent
+
+### Changes Summary
+```typescript
+// Now properly typed in TypeScript
+interface OnairosCompleteData {
+  token: string;        // ✅ JWT token for authenticated API calls
+  apiUrl: string;       // ✅ Backend API endpoint URL
+  // ... plus 20+ optional fields with full documentation
+}
+
+// Usage
+const handleComplete = (data: OnairosCompleteData) => {
+  const { token, apiUrl } = data; // TypeScript knows these are strings!
+};
+```
+
+## [3.4.0] - 2024-10-09
+
+### 🚀 Major Features
+
+#### Standardized API Key Validation System
+- **NEW**: Implemented comprehensive `initializeApiKey()` function following standardized documentation
+- **NEW**: Added `validateApiKey()` utility with backend validation
+- **NEW**: Created `/auth/validate-key` endpoint for standardized API key validation
+- **NEW**: Added retry logic with exponential backoff for network resilience
+- **NEW**: Comprehensive error handling with specific error codes and suggestions
+
+#### Enhanced SDK Architecture
+- **NEW**: Modular API key validation utilities (`apiKeyValidation.js`)
+- **NEW**: Centralized SDK initialization system (`sdkInitialization.js`)
+- **NEW**: Global SDK state management with proper lifecycle
+- **NEW**: Authenticated request helper with automatic API key injection
+
+#### ChatGPT Integration
+- **NEW**: Added ChatGPT as first connector with special behavior
+- **NEW**: ChatGPT connector opens `chatgpt.com` in new tab (no OAuth)
+- **NEW**: Added OpenAI icon support with fallback to emoji
+- **NEW**: Updated platform configurations across all components
+
+#### Gmail OAuth Fix
+- **NEW**: Created Gmail OAuth backend route (`gmail-enhanced.js`)
+- **NEW**: Added Gmail configuration to OAuth config
+- **NEW**: Fixed "Not Found" error for Gmail authorization
+- **NEW**: Comprehensive Gmail OAuth flow with token exchange
+
+### 🔧 Technical Improvements
+
+#### API Key Validation
+- **Format Validation**: Supports `ona_`, `dev_`, `pk_` prefixes (32+ characters)
+- **Admin Key Support**: Special handling for admin keys with full permissions
+- **Environment Detection**: Automatic production/development environment detection
+- **Rate Limiting**: Built-in rate limit handling and reporting
+- **Timeout Handling**: Configurable timeouts with abort controller
+
+#### Error Handling
+- **Standardized Error Codes**: `MISSING_API_KEY`, `INVALID_API_KEY_FORMAT`, etc.
+- **Detailed Error Messages**: User-friendly error descriptions
+- **Actionable Suggestions**: Specific suggestions for each error type
+- **Retry Logic**: Automatic retry with exponential backoff for server errors
+
+#### SDK Configuration
+```typescript
+interface InitConfig {
+  apiKey: string;                    // Required: Developer API key
+  environment?: 'production' | 'development'; // Default: auto-detected
+  enableLogging?: boolean;           // Default: false
+  timeout?: number;                  // Default: 30000ms
+  retryAttempts?: number;            // Default: 3
+  platform?: string;                // Default: 'web'
+  sdkVersion?: string;               // Default: '3.4.0'
+}
+```
+
+### 📡 API Endpoints
+
+#### New Validation Endpoints
+- **POST** `/auth/validate-key` - Primary validation endpoint
+- **GET** `/auth/validate-key?key=API_KEY` - Simple validation
+- **GET** `/auth/health` - Health check endpoint
+
+#### Enhanced OAuth Endpoints
+- **POST** `/gmail/authorize` - Gmail OAuth authorization
+- **GET** `/gmail/callback` - Gmail OAuth callback
+- **POST** `/gmail/native-auth` - Gmail native authentication
+
+### 🎨 UI/UX Improvements
+
+#### Platform Connectors
+- **ChatGPT First**: ChatGPT appears as first connector option
+- **Visual Icons**: OpenAI icon for ChatGPT with emoji fallback
+- **Consistent Design**: Unified design across all connector components
+- **Special Behaviors**: Platform-specific behaviors (ChatGPT opens new tab)
+
+#### Error Feedback
+- **User-Friendly Messages**: Clear error descriptions for users
+- **Developer Guidance**: Detailed suggestions for developers
+- **Visual Feedback**: Proper loading states and error indicators
+
+### 🔒 Security Enhancements
+
+#### API Key Security
+- **Format Validation**: Strict format validation before network requests
+- **Secure Storage**: Proper API key handling in global state
+- **Token Management**: Automatic token refresh and management
+- **Permission Checking**: Granular permission validation
+
+#### Network Security
+- **HTTPS Only**: All API calls use HTTPS endpoints
+- **Request Signing**: Proper authorization headers
+- **Timeout Protection**: Request timeout protection
+- **Retry Limits**: Bounded retry attempts to prevent abuse
+
+### 📚 Documentation
+
+#### New Documentation Files
+- `SDK_API_KEY_VALIDATION.md` - Comprehensive API key validation guide
+- `GMAIL_CHATGPT_IMPLEMENTATION.md` - Gmail OAuth and ChatGPT implementation
+- `CHATGPT_ICON_UPDATE.md` - ChatGPT icon implementation details
+- `CHANGELOG.md` - This changelog
+
+#### Code Documentation
+- **JSDoc Comments**: Comprehensive function documentation
+- **TypeScript Interfaces**: Proper type definitions
+- **Usage Examples**: Clear usage examples in documentation
+- **Error Handling**: Documented error codes and handling
+
+### 🧪 Testing & Quality
+
+#### Validation Testing
+- **Format Validation**: Comprehensive API key format testing
+- **Network Testing**: Retry logic and timeout testing
+- **Error Scenarios**: All error code paths tested
+- **Integration Testing**: End-to-end validation flow testing
+
+#### Code Quality
+- **ESLint Clean**: No linting errors
+- **Modular Design**: Clean separation of concerns
+- **Error Boundaries**: Proper error handling throughout
+- **Performance**: Optimized network requests and state management
+
+### 🔄 Migration Guide
+
+#### From v3.3.0 to v3.4.0
+
+**Before (v3.3.0)**:
+```javascript
+import { OnairosButton } from 'onairos';
+
+// Components worked without explicit initialization
+<OnairosButton requestData={{...}} />
+```
+
+**After (v3.4.0)**:
+```javascript
+import { initializeApiKey, OnairosButton } from 'onairos';
+
+// 1. Initialize SDK first
+await initializeApiKey({
+  apiKey: 'ona_your_api_key_here',
+  environment: 'production',
+  enableLogging: true
+});
+
+// 2. Use components (they automatically use initialized API key)
+<OnairosButton requestData={{...}} />
+```
+
+#### Breaking Changes
+- **API Key Required**: `initializeApiKey()` must be called before using SDK components
+- **Environment Detection**: Automatic environment detection (can be overridden)
+- **Error Handling**: New error codes and error structure
+
+#### Backward Compatibility
+- **Component APIs**: All existing component APIs remain unchanged
+- **Response Formats**: All response formats remain compatible
+- **OAuth Flows**: Existing OAuth flows continue to work
+
+### 🐛 Bug Fixes
+
+#### Gmail OAuth
+- **Fixed**: "Not Found" error when connecting Gmail
+- **Fixed**: Missing Gmail OAuth backend route
+- **Fixed**: Gmail OAuth callback handling
+- **Fixed**: Gmail token exchange and user data storage
+
+#### Platform Connectors
+- **Fixed**: Platform icon loading and fallback behavior
+- **Fixed**: Connector state management across components
+- **Fixed**: Platform configuration consistency
+- **Fixed**: Special behavior handling for different platforms
+
+#### SDK Initialization
+- **Fixed**: Race conditions in SDK initialization
+- **Fixed**: Global state management and cleanup
+- **Fixed**: Error propagation and handling
+- **Fixed**: Network request timeout and retry logic
+
+### 📦 Dependencies
+
+#### Updated Dependencies
+- Maintained compatibility with existing React versions
+- No breaking dependency changes
+- Added proper error handling utilities
+- Enhanced network request capabilities
+
+### 🚀 Deployment
+
+#### NPM Package
+- **Version**: 3.4.0
+- **Size**: Optimized bundle size
+- **Compatibility**: React 18+, Node.js 16+
+- **Platforms**: Web, React Native, Node.js
+
+#### Distribution Files
+- `dist/onairos.bundle.js` - Browser bundle
+- `dist/onairos.esm.js` - ES modules
+- `dist/onairos.native.js` - React Native
+- `dist/onairos.laravel.js` - Laravel integration
+
+---
+
+## [3.3.0] - Previous Release
+
+### Features
+- Basic OAuth connectors
+- Component-based data collection
+- Response formatting utilities
+
+---
+
+*For more details, see the [GitHub repository](https://github.com/zd819/onairos-npm) and [documentation](https://docs.onairos.uk).*

package/lib/commonjs/constants/index.js

@@ -4,4 +4,4 @@ var __ONAIROS_REQ_REGISTRY__ = [
     require("../config/api")
 ];
 function __ONAIROS_REQ_FUNC__(i) { return __ONAIROS_REQ_REGISTRY__[i]; }
-function _0x5c12(_0x1f4341,_0x5c1233){_0x1f4341=_0x1f4341-0x0;const _0x12fd02=_0x1f43();let _0x2d7dcb=_0x12fd02[_0x1f4341];return _0x2d7dcb;}Object[_0x5c12(0x0)](exports,_0x5c12(0x1),{'value':!![]}),exports[_0x5c12(0x2)]=exports[_0x5c12(0x3)]=exports[_0x5c12(0x4)]=exports[_0x5c12(0x5)]=exports[_0x5c12(0x6)]=exports[_0x5c12(0x7)]=void 0x0;function _0x1f43(){const _0x5c2db3=['defineProperty','__esModule','STORAGE_KEYS','PLATFORMS','PIN_REQUIREMENTS','DEEP_LINK_CONFIG','COLORS','API_ENDPOINTS','#1BA9D4','#F8F9FA','#000000','#666666','#E5E5E5','#34C759','#FF3B30','#E60023','#FF4500','#10A37F','Instagram','instagram','Connect\x20your\x20Instagram\x20account\x20to\x20train\x20your\x20AI\x20model','Reddit','reddit','Connect\x20Reddit\x20to\x20enhance\x20your\x20AI\x20model','youtube','Use\x20YouTube\x20data\x20to\x20improve\x20AI\x20recommendations','ChatGPT','chat','chatgpt','psychology','llm','Connect\x20your\x20AI\x20conversation\x20data','BASE_URL','/instagram/auth','/pinterest/auth','/reddit/auth','/youtube/auth','/chatgpt/auth','/instagram/callback','/pinterest/callback','/reddit/callback','/chatgpt/callback','/llmdata','/llmdata/request','onairos_credentials','onairos_connections','onairosanime','authenticate','onairosanime://auth/'];_0x1f43=function(){return _0x5c2db3;};return _0x1f43();}var _api=__ONAIROS_REQ_FUNC__(0x0);const COLORS=exports['COLORS']={'primary':_0x5c12(0x8),'headerBg':_0x5c12(0x9),'text':{'primary':_0x5c12(0xa),'secondary':_0x5c12(0xb)},'border':_0x5c12(0xc),'success':_0x5c12(0xd),'error':_0x5c12(0xe),'instagram':'#E1306C','pinterest':_0x5c12(0xf),'reddit':_0x5c12(0x10),'youtube':'#FF0000','chatgpt':_0x5c12(0x11),'llm':_0x5c12(0x11),'white':'#FFFFFF','black':_0x5c12(0xa),'gray':_0x5c12(0xb),'lightGray':_0x5c12(0xc)},PLATFORMS=exports['PLATFORMS']={'instagram':{'name':_0x5c12(0x12),'icon':_0x5c12(0x13),'color':COLORS[_0x5c12(0x13)],'description':_0x5c12(0x14)},'pinterest':{'name':'Pinterest','icon':'pinterest','color':COLORS['pinterest'],'description':'Use\x20your\x20Pinterest\x20boards\x20for\x20AI\x20training'},'reddit':{'name':_0x5c12(0x15),'icon':'reddit','color':COLORS[_0x5c12(0x16)],'description':_0x5c12(0x17)},'youtube':{'name':'YouTube','icon':_0x5c12(0x18),'color':COLORS['youtube'],'description':_0x5c12(0x19)},'chatgpt':{'name':_0x5c12(0x1a),'icon':_0x5c12(0x1b),'color':COLORS[_0x5c12(0x1c)],'description':'Connect\x20your\x20ChatGPT\x20conversations\x20for\x20AI\x20insights'},'llm':{'name':'LLM\x20Data','icon':_0x5c12(0x1d),'color':COLORS[_0x5c12(0x1e)],'description':_0x5c12(0x1f)}},API_ENDPOINTS=exports[_0x5c12(0x7)]={'base':_api['API_CONFIG'][_0x5c12(0x20)],'oauth':{'instagram':_0x5c12(0x21),'pinterest':_0x5c12(0x22),'reddit':_0x5c12(0x23),'youtube':_0x5c12(0x24),'chatgpt':_0x5c12(0x25),'llm':'/chatgpt/auth'},'callback':{'instagram':_0x5c12(0x26),'pinterest':_0x5c12(0x27),'reddit':_0x5c12(0x28),'youtube':'/youtube/callback','chatgpt':_0x5c12(0x29),'llm':_0x5c12(0x29)},'llm':{'dataIngest':_0x5c12(0x2a),'dataRequest':_0x5c12(0x2b)}},STORAGE_KEYS=exports[_0x5c12(0x2)]={'credentials':_0x5c12(0x2c),'connections':_0x5c12(0x2d)},PIN_REQUIREMENTS=exports[_0x5c12(0x4)]={'minLength':0x8,'requireUppercase':!![],'requireLowercase':!![],'requireNumber':!![],'requireSpecialChar':!![]},DEEP_LINK_CONFIG=exports[_0x5c12(0x5)]={'scheme':_0x5c12(0x2e),'host':_0x5c12(0x2f),'redirectUri':_0x5c12(0x30)};
+function _0x4e8f(_0x146c9c,_0x4e8f4f){_0x146c9c=_0x146c9c-0x0;const _0x5bbbeb=_0x146c();let _0x44d736=_0x5bbbeb[_0x146c9c];return _0x44d736;}Object[_0x4e8f(0x0)](exports,_0x4e8f(0x1),{'value':!![]}),exports[_0x4e8f(0x2)]=exports['PLATFORMS']=exports[_0x4e8f(0x3)]=exports[_0x4e8f(0x4)]=exports[_0x4e8f(0x5)]=exports['API_ENDPOINTS']=void 0x0;var _api=__ONAIROS_REQ_FUNC__(0x0);const COLORS=exports[_0x4e8f(0x5)]={'primary':'#1BA9D4','headerBg':_0x4e8f(0x6),'text':{'primary':_0x4e8f(0x7),'secondary':_0x4e8f(0x8)},'border':_0x4e8f(0x9),'success':'#34C759','error':_0x4e8f(0xa),'instagram':_0x4e8f(0xb),'pinterest':_0x4e8f(0xc),'reddit':_0x4e8f(0xd),'youtube':_0x4e8f(0xe),'chatgpt':_0x4e8f(0xf),'llm':_0x4e8f(0xf),'white':'#FFFFFF','black':_0x4e8f(0x7),'gray':_0x4e8f(0x8),'lightGray':_0x4e8f(0x9)},PLATFORMS=exports['PLATFORMS']={'instagram':{'name':_0x4e8f(0x10),'icon':_0x4e8f(0x11),'color':COLORS[_0x4e8f(0x11)],'description':_0x4e8f(0x12)},'pinterest':{'name':'Pinterest','icon':'pinterest','color':COLORS[_0x4e8f(0x13)],'description':_0x4e8f(0x14)},'reddit':{'name':_0x4e8f(0x15),'icon':_0x4e8f(0x16),'color':COLORS[_0x4e8f(0x16)],'description':'Connect\x20Reddit\x20to\x20enhance\x20your\x20AI\x20model'},'youtube':{'name':'YouTube','icon':'youtube','color':COLORS[_0x4e8f(0x17)],'description':_0x4e8f(0x18)},'chatgpt':{'name':_0x4e8f(0x19),'icon':_0x4e8f(0x1a),'color':COLORS[_0x4e8f(0x1b)],'description':_0x4e8f(0x1c)},'llm':{'name':_0x4e8f(0x1d),'icon':'psychology','color':COLORS[_0x4e8f(0x1e)],'description':_0x4e8f(0x1f)}},API_ENDPOINTS=exports[_0x4e8f(0x20)]={'base':_api['API_CONFIG']['BASE_URL'],'oauth':{'instagram':_0x4e8f(0x21),'pinterest':'/pinterest/auth','reddit':_0x4e8f(0x22),'youtube':_0x4e8f(0x23),'chatgpt':_0x4e8f(0x24),'llm':_0x4e8f(0x24)},'callback':{'instagram':_0x4e8f(0x25),'pinterest':'/pinterest/callback','reddit':_0x4e8f(0x26),'youtube':_0x4e8f(0x27),'chatgpt':_0x4e8f(0x28),'llm':_0x4e8f(0x28)},'llm':{'dataIngest':'/llmdata','dataRequest':'/llmdata/request'}},STORAGE_KEYS=exports['STORAGE_KEYS']={'credentials':_0x4e8f(0x29),'connections':_0x4e8f(0x2a)},PIN_REQUIREMENTS=exports[_0x4e8f(0x3)]={'minLength':0x8,'requireUppercase':!![],'requireLowercase':!![],'requireNumber':!![],'requireSpecialChar':!![]},DEEP_LINK_CONFIG=exports[_0x4e8f(0x4)]={'scheme':_0x4e8f(0x2b),'host':_0x4e8f(0x2c),'redirectUri':'onairosanime://auth/'};function _0x146c(){const _0x48af4f=['defineProperty','__esModule','STORAGE_KEYS','PIN_REQUIREMENTS','DEEP_LINK_CONFIG','COLORS','#F8F9FA','#000000','#666666','#E5E5E5','#FF3B30','#E1306C','#E60023','#FF4500','#FF0000','#10A37F','Instagram','instagram','Connect\x20your\x20Instagram\x20account\x20to\x20train\x20your\x20AI\x20model','pinterest','Use\x20your\x20Pinterest\x20boards\x20for\x20AI\x20training','Reddit','reddit','youtube','Use\x20YouTube\x20data\x20to\x20improve\x20AI\x20recommendations','ChatGPT','chat','chatgpt','Connect\x20your\x20ChatGPT\x20conversations\x20for\x20AI\x20insights','LLM\x20Data','llm','Connect\x20your\x20AI\x20conversation\x20data','API_ENDPOINTS','/instagram/auth','/reddit/auth','/youtube/auth','/chatgpt/auth','/instagram/callback','/reddit/callback','/youtube/callback','/chatgpt/callback','onairos_credentials','onairos_connections','onairosanime','authenticate'];_0x146c=function(){return _0x48af4f;};return _0x146c();}