Resolve expo 54 and react native 0.82.0 conflict

Author: eyovvalupe

IOS_BUILD_INSTRUCTIONS.md

@@ -0,0 +1,137 @@
+# iOS Build Instructions
+
+## Summary
+This project uses React Native 0.82.0 with Expo modules to support the `@playerdata/react-native-mcu-manager` library. A compatibility patch has been applied to fix iOS build errors.
+
+## Prerequisites
+- macOS with Xcode installed
+- CocoaPods installed (`sudo gem install cocoapods`)
+- Node.js 20+ installed
+
+## Build Steps
+
+### 1. Install Dependencies
+```bash
+npm install
+```
+
+The `postinstall` script will automatically apply the expo-modules-core iOS compatibility patch.
+
+### 2. Install iOS Pods
+```bash
+cd ios
+pod install
+cd ..
+```
+
+### 3. Build for iOS
+```bash
+npm run ios
+```
+
+Or open in Xcode:
+```bash
+open ios/IotDfu.xcworkspace
+```
+
+## What Was Fixed
+
+### Problem
+The error `No member named 'CallInvoker' in namespace 'facebook::react'` occurred because:
+- Expo SDK 54 (`expo-modules-core@3.0.24`) was designed for React Native 0.81
+- React Native 0.82 changed the location of the `CallInvoker` class on iOS
+
+### Solution
+Applied a patch to add missing imports in two files:
+1. `node_modules/expo-modules-core/ios/JSI/EXJSIUtils.h`
+2. `node_modules/expo-modules-core/ios/JSI/EXJavaScriptRuntime.h`
+
+Both files now include:
+```objc
+#import <ReactCommon/CallInvoker.h>
+```
+
+### Patch Details
+- The patch is located in `patches/` directory
+- Automatically applied via `postinstall` script in `package.json`
+- Can be manually applied:
+  - macOS/Linux: `bash patches/expo-modules-core-fix.sh`
+  - Windows: `patches\expo-modules-core-fix.bat`
+
+## Configuration Files
+
+### iOS Files Modified for Expo Modules:
+
+1. **ios/Podfile**
+   - Added Expo autolinking script
+   - Added `use_expo_modules!` in target block
+
+2. **ios/IotDfu/AppDelegate.swift**
+   - Added `import ExpoModulesCore`
+   - Added `extraModules(for:)` method to register Expo modules
+
+### Android Files Modified for Expo Modules:
+
+1. **android/settings.gradle**
+   - Added Expo autolinking configuration
+
+2. **android/app/build.gradle**
+   - Configured for Expo modules
+
+3. **android/app/src/main/java/com/iotdfu/MainApplication.kt**
+   - Integrated `ApplicationLifecycleDispatcher` for Expo modules
+
+## Status
+
+✅ **Android Build**: Working perfectly with React Native 0.82 + Expo SDK 54
+❓ **iOS Build**: Patch applied, needs testing on macOS
+
+## Testing the App
+
+Once the iOS build succeeds, test the following:
+1. App launches without "Cannot read property 'EventEmitter' of undefined" error
+2. BLE scanning works
+3. MCU Manager firmware update functionality works
+4. Device connection and communication work as expected
+
+## Troubleshooting
+
+### If iOS build still fails:
+1. Clean the build:
+   ```bash
+   cd ios
+   rm -rf Pods Podfile.lock
+   pod install
+   cd ..
+   ```
+
+2. Clean Xcode build folder:
+   - Open Xcode
+   - Product → Clean Build Folder (Shift+Cmd+K)
+
+3. Verify the patch was applied:
+   ```bash
+   grep "ReactCommon/CallInvoker.h" node_modules/expo-modules-core/ios/JSI/EXJSIUtils.h
+   grep "ReactCommon/CallInvoker.h" node_modules/expo-modules-core/ios/JSI/EXJavaScriptRuntime.h
+   ```
+   Both commands should return a line showing the import.
+
+### If you need to reapply the patch:
+```bash
+bash patches/expo-modules-core-fix.sh
+```
+
+## Future Considerations
+
+This patch is a temporary workaround. When Expo SDK 55 is released with official React Native 0.82 support, you can:
+1. Update to Expo SDK 55
+2. Remove the patch files and postinstall script
+3. Update dependencies
+
+## Additional Notes
+
+- The Android build is fully working and tested
+- The iOS configuration is complete and should work once built on macOS
+- Both platforms use the same Expo modules integration
+- The MCU Manager library requires Expo modules - there is no way to use it without Expo
+