The LiveKitClient CocoaPod on trunk caps at 2.0.18 (2.1+ is SPM-only), so the 2.15 CallKit audio API was unreachable. BUT the repo still ships a valid podspec at tag 2.15.3, and its deps (LiveKitWebRTC 144.7559.11, LiveKitUniFFI 0.0.6, SwiftProtobuf) ARE on trunk. So instead of a risky SPM migration: - ios-patch.sh injects `pod 'LiveKitClient', :git => <repo>, :tag => '2.15.3'` into the generated Podfile (after cap sync, before pod install). The NativeCall podspec's '~> 2.0' is satisfied by 2.15.3. Idempotent; hard-fails if it can't find the App target so we never silently fall back to 2.0.18. - Plugin re-adds the CallKit<->LiveKit audio-session coordination, now compilable: auto-config OFF + engine OFF at load; configure session + enable engine in didActivate; disable in didDeactivate; request mic permission on connect. Core Room APIs (connect/disconnect/setMicrophone) verified compatible between 2.0.18 and 2.15.3 against the real source. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Biz Connect — Mobile app (Capacitor)
A Capacitor shell that loads the live Connect web UI (server.url in
capacitor.config.json) and adds native push, camera/mic, and store distribution. See the
overall plan in ../CLIENTS.md.
Android: follow the step-by-step in ANDROID_SETUP.md (project generation, icons/splash, permissions, Firebase/FCM, run, and Play Store build).
Prerequisites
- Node +
npm installhere. - Android: Android Studio + SDK.
- iOS: macOS + Xcode (+ an Apple Developer account to run on device / ship).
Setup
npm install
npm run assets # generate app icons + splash from resources/
npx cap add android
npx cap add ios # macOS only
npx cap sync
Run / build
npx cap open android # build & run from Android Studio
npx cap open ios # build & run from Xcode
Server origin
The app loads server.url from capacitor.config.json (default
https://remote.bizgaze.com). For a local device test against a dev server, set it to your
machine's LAN URL (and allow cleartext for plain http).
Native push (next step)
Native push uses the Capacitor Push Notifications plugin (FCM on Android, APNs on iOS) and a server endpoint to register device tokens — tracked in ../CLIENTS.md Phase B. This is separate from the existing Web Push (VAPID) the PWA already uses. Needs Google/Apple credentials to test end-to-end.
Shipping (gated on accounts)
- Google Play: one-time $25; upload an AAB; signing key.
- App Store: Apple Developer $99/yr; archive via Xcode; App Store Connect listing.