feat: Implement Thread-Safe Concurrency with Swift Actors and Kotlin Atomic Operations #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Overview
This PR introduces comprehensive thread-safety improvements using modern concurrency patterns - Swift Actors for iOS and Kotlin atomic operations with synchronized locks for Android.
🔄 What Changed
iOS Improvements
CameraSessionActorandCallbackActorfor isolated state managementCameraViewdeinitRCTEventEmitterinheritance in favor ofNativeReactNativeScannerSpecBaseAndroid Improvements
@SynchronizedwithAtomicBooleanandAtomicReferenceReactNativeScannerViewTypeScript/JavaScript
addListener/removeListenersmethodsBarcodeScannedEvent📊 Technical Details
Thread Safety Patterns
🐛 Bugs Fixed
startScanning()between permission check and flag setIllegalStateException🔧 Migration Guide
Breaking Changes
NativeEventEmitter- uses Codegen events automaticallycurrentSession()replaced with asyncgetCurrentSession(completion:)Before (v1.x):
After (v2.0.0):
📈 Performance Impact
📝 Documentation