microsoft / react-native-code-push

React Native module for CodePush
http://appcenter.ms
Other
8.93k stars 1.46k forks source link

Mandatory updates to codepush are crashing app #2729

Closed mljlynch closed 3 weeks ago

mljlynch commented 1 month ago

Thanks so much for filing an issue or feature request! Please fill out the following (wherever relevant):

Steps to Reproduce

  1. Set Up app to rn 0.71
  2. React-native-code-push 8.1.0
  3. Deploy a bundle to the codepush server
  4. mark as required

Expected Behavior

What you expected to happen?

Actual Behavior

EXC_BREAKPOINT - MLKITx_SRLRegistrySharedInstanceForProviders in _objc_initiateDealloc

Environment

MikhailSuendukov commented 1 month ago

Hello, thank you for reaching out to us. Could you please let us know if this issue is reproducible with react-native-code-push version 8.3.0? Additionally, it would be very helpful if you could provide the logs preceding the error along with a full stack trace or crash report representing this error.

RobinChiHsu commented 1 month ago

Can you show your Podfile?

mljlynch commented 1 month ago

I've updated to 8.3.1. And this is still happening.

This is the full stacktrace: ``` OS Version: iOS 17.5.1 (21F90) Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Crashed Thread: 10 Application Specific Information: _objc_initiateDealloc Thread 10 Crashed: 0 Fig 0x205fadd48 MLKITx_SRLRegistrySharedInstanceForProviders 1 Fig 0x205fb0bd4 MLKITx_SRLRegistrySharedInstanceForProviders 2 libobjc.A.dylib 0x3198281f0 AutoreleasePoolPage::releaseUntil 3 libobjc.A.dylib 0x31982807c objc_autoreleasePoolPop 4 CoreFoundation 0x329a12df8 _CFAutoreleasePoolPop 5 Foundation 0x3277faad4 __NSThreadPerformPerform 6 CoreFoundation 0x329a44830 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 7 CoreFoundation 0x329a447c4 __CFRunLoopDoSource0 8 CoreFoundation 0x329a42294 __CFRunLoopDoSources0 9 CoreFoundation 0x329a41480 __CFRunLoopRun 10 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 11 Fig 0x205d43870 MLKITx_SRLRegistrySharedInstanceForProviders 12 Foundation 0x327824714 __NSThread__start__ 13 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 0 0 libsystem_platform.dylib 0x3e3633e1c _platform_strcmp 1 libicucore.A.dylib 0x33cc0ee28 res_getTableItemByKey 2 libicucore.A.dylib 0x33cc0ecf0 res_getTableItemByKey 3 libicucore.A.dylib 0x33cc0f3d8 icu::ResourceArray::getValue 4 libicucore.A.dylib 0x33cc09360 ures_getByKeyWithFallback 5 libicucore.A.dylib 0x33cc08fc4 ures_getStringByKeyWithFallback 6 libicucore.A.dylib 0x33ccd2e74 icu::number::impl::Grouper::setLocaleData 7 libicucore.A.dylib 0x33ccd2d94 icu::number::impl::Grouper::setLocaleData 8 libicucore.A.dylib 0x33ccd1b1c icu::number::LocalizedNumberFormatter::getDecimalFormatSymbols 9 libicucore.A.dylib 0x33ccd0a84 icu::number::LocalizedNumberFormatter::getDecimalFormatSymbols 10 libicucore.A.dylib 0x33cccfeac icu::number::LocalizedNumberFormatter::formatImpl 11 libicucore.A.dylib 0x33cc74d9c icu::DecimalFormat::format 12 libicucore.A.dylib 0x33ccec0f4 icu::NumberFormat::format 13 libicucore.A.dylib 0x33cd822e8 unum_formatDecimal 14 CoreFoundation 0x329a8f3b4 __cficu_unum_formatDecimal 15 CoreFoundation 0x329a8ec88 CFNumberFormatterCreateStringWithNumber 16 Foundation 0x3277ee6b0 -[NSNumberFormatter stringForObjectValue:] 17 UIKitCore 0x32e98f044 -[_UIDatePickerCalendarTimeFormat localizedTimeStringWithHours:minutes:isPM:ranges:] 18 UIKitCore 0x32e59a600 -[_UIDatePickerCalendarTimeLabel attributedTextWithRanges:] 19 UIKitCore 0x32ede06b4 -[_UIDatePickerCompactTimeLabel pushCurrentStateIntoUI] 20 UIKitCore 0x32e59ac78 -[_UIDatePickerCalendarTimeLabel setTimeFormat:] 21 UIKitCore 0x32ede19bc -[_UIDatePickerCompactTimeLabel reloadWithCalendar:locale:followsSystemHourCycle:displaysTimeZone:] 22 UIKitCore 0x32f085838 -[_UIDatePickerIOSCompactView _reloadTimeViewTimeFormat] 23 UIKitCore 0x32f082f80 -[_UIDatePickerIOSCompactView _updateUI] 24 UIKitCore 0x32f085928 -[_UIDatePickerIOSCompactView setData:] 25 UIKitCore 0x32ed6d820 -[UIDatePicker _installPickerView:updatingSize:] 26 UIKitCore 0x32ed6cb80 -[UIDatePicker initWithFrame:] 27 Fig 0x205c87d90 MLKITx_SRLRegistrySharedInstanceForProviders 28 Fig 0x205c88700 MLKITx_SRLRegistrySharedInstanceForProviders 29 Fig 0x205d5d594 MLKITx_SRLRegistrySharedInstanceForProviders 30 Fig 0x205d5d9fc MLKITx_SRLRegistrySharedInstanceForProviders 31 Fig 0x205d89bbc MLKITx_SRLRegistrySharedInstanceForProviders 32 Fig 0x205d5e4ec MLKITx_SRLRegistrySharedInstanceForProviders 33 Fig 0x205d46ecc MLKITx_SRLRegistrySharedInstanceForProviders 34 libdispatch.dylib 0x33983a138 _dispatch_call_block_and_release 35 libdispatch.dylib 0x33983bdd0 _dispatch_client_callout 36 libdispatch.dylib 0x33984a5e8 _dispatch_main_queue_drain 37 libdispatch.dylib 0x33984a1b4 _dispatch_main_queue_callback_4CF 38 CoreFoundation 0x329a4470c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ 39 CoreFoundation 0x329a41910 __CFRunLoopRun 40 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 41 GraphicsServices 0x3b37f31a4 GSEventRunModal 42 UIKitCore 0x32e2fa908 -[UIApplication _run] 43 UIKitCore 0x32e3ae9cc UIApplicationMain 44 Fig 0x204f14050 45 0x1c4f25e4c Thread 1 0 libsystem_pthread.dylib 0x3e379b0c4 start_wqthread Thread 2 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 3 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 4 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 5 name: com.apple.uikit.eventfetch-thread 0 libsystem_kernel.dylib 0x3bbc53808 mach_msg2_trap 1 libsystem_kernel.dylib 0x3bbc57004 mach_msg2_internal 2 libsystem_kernel.dylib 0x3bbc56f1c mach_msg_overwrite 3 libsystem_kernel.dylib 0x3bbc56d5c mach_msg 4 CoreFoundation 0x329a41f58 __CFRunLoopServiceMachPort 5 CoreFoundation 0x329a415fc __CFRunLoopRun 6 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 7 Foundation 0x32780de48 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] 8 Foundation 0x32780dc98 -[NSRunLoop(NSRunLoop) runUntilDate:] 9 UIKitCore 0x32e30e63c -[UIEventFetcher threadMain] 10 Foundation 0x327824714 __NSThread__start__ 11 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 6 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 7 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 8 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 9 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 10 name: com.facebook.react.JavaScript Crashed: 0 Fig 0x205fadd48 MLKITx_SRLRegistrySharedInstanceForProviders 1 Fig 0x205fb0bd4 MLKITx_SRLRegistrySharedInstanceForProviders 2 libobjc.A.dylib 0x3198281f0 AutoreleasePoolPage::releaseUntil 3 libobjc.A.dylib 0x31982807c objc_autoreleasePoolPop 4 CoreFoundation 0x329a12df8 _CFAutoreleasePoolPop 5 Foundation 0x3277faad4 __NSThreadPerformPerform 6 CoreFoundation 0x329a44830 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 7 CoreFoundation 0x329a447c4 __CFRunLoopDoSource0 8 CoreFoundation 0x329a42294 __CFRunLoopDoSources0 9 CoreFoundation 0x329a41480 __CFRunLoopRun 10 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 11 Fig 0x205d43870 MLKITx_SRLRegistrySharedInstanceForProviders 12 Foundation 0x327824714 __NSThread__start__ 13 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 11 name: com.apple.NSURLConnectionLoader 0 libsystem_kernel.dylib 0x3bbc53808 mach_msg2_trap 1 libsystem_kernel.dylib 0x3bbc57004 mach_msg2_internal 2 libsystem_kernel.dylib 0x3bbc56f1c mach_msg_overwrite 3 libsystem_kernel.dylib 0x3bbc56d5c mach_msg 4 CoreFoundation 0x329a41f58 __CFRunLoopServiceMachPort 5 CoreFoundation 0x329a415fc __CFRunLoopRun 6 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 7 CFNetwork 0x32bd57c8c _CFHostIsDomainTopLevel 8 Foundation 0x327824714 __NSThread__start__ 9 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 12 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 13 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 14 0 libsystem_kernel.dylib 0x3bbc53590 __workq_kernreturn 1 libsystem_pthread.dylib 0x3e379e97c _pthread_wqthread Thread 15 name: com.apple.CoreMotion.MotionThread 0 libsystem_kernel.dylib 0x3bbc53808 mach_msg2_trap 1 libsystem_kernel.dylib 0x3bbc57004 mach_msg2_internal 2 libsystem_kernel.dylib 0x3bbc56f1c mach_msg_overwrite 3 libsystem_kernel.dylib 0x3bbc56d5c mach_msg 4 CoreFoundation 0x329a41f58 __CFRunLoopServiceMachPort 5 CoreFoundation 0x329a415fc __CFRunLoopRun 6 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 7 CoreFoundation 0x329aaef00 CFRunLoopRun 8 CoreMotion 0x3434a4210 9 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 16 0 libsystem_kernel.dylib 0x3bbc593ec __semwait_signal 1 libsystem_c.dylib 0x3398dc5ec nanosleep 2 libsystem_c.dylib 0x339939728 sleep 3 Fig 0x205fe87f4 MLKITx_SRLRegistrySharedInstanceForProviders 4 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 17 name: SentryCrash Exception Handler (Secondary) 0 libsystem_kernel.dylib 0x3bbc53808 mach_msg2_trap 1 libsystem_kernel.dylib 0x3bbc57004 mach_msg2_internal 2 libsystem_kernel.dylib 0x3bbc56f1c mach_msg_overwrite 3 libsystem_kernel.dylib 0x3bbc56d5c mach_msg 4 Fig 0x205ff453c __cxa_throw 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 19 name: io.sentry.app-hang-tracker 0 libsystem_kernel.dylib 0x3bbc593ec __semwait_signal 1 libsystem_c.dylib 0x3398dc5ec nanosleep 2 Foundation 0x327960710 +[NSThread sleepForTimeInterval:] 3 Fig 0x205fd7534 MLKITx_SRLRegistrySharedInstanceForProviders 4 Foundation 0x327824714 __NSThread__start__ 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 20 0 libsystem_kernel.dylib 0x3bbc53808 mach_msg2_trap 1 libsystem_kernel.dylib 0x3bbc57004 mach_msg2_internal 2 libsystem_kernel.dylib 0x3bbc56f1c mach_msg_overwrite 3 libsystem_kernel.dylib 0x3bbc56d5c mach_msg 4 CoreFoundation 0x329a41f58 __CFRunLoopServiceMachPort 5 CoreFoundation 0x329a415fc __CFRunLoopRun 6 CoreFoundation 0x329a40cd4 CFRunLoopRunSpecific 7 Fig 0x205d43870 MLKITx_SRLRegistrySharedInstanceForProviders 8 Foundation 0x327824714 __NSThread__start__ 9 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 21 0 libsystem_kernel.dylib 0x3bbc591cc __psynch_cvwait 1 libsystem_pthread.dylib 0x3e379d6e0 _pthread_cond_wait 2 libc++.1.dylib 0x34a253500 std::__1::condition_variable::wait 3 hermes 0x109064ca8 facebook::jsi::JSError::~JSError 4 hermes 0x109064a5c facebook::jsi::JSError::~JSError 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 22 0 libsystem_kernel.dylib 0x3bbc591cc __psynch_cvwait 1 libsystem_pthread.dylib 0x3e379d6e0 _pthread_cond_wait 2 libc++.1.dylib 0x34a253500 std::__1::condition_variable::wait 3 Fig 0x206660fb0 absl::lts_20220623::internal_any_invocable::LocalManagerNontrivial 4 Fig 0x206616958 absl::lts_20220623::internal_any_invocable::LocalManagerNontrivial 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 23 0 libsystem_kernel.dylib 0x3bbc591cc __psynch_cvwait 1 libsystem_pthread.dylib 0x3e379d6e0 _pthread_cond_wait 2 libc++.1.dylib 0x34a253500 std::__1::condition_variable::wait 3 Fig 0x206660fb0 absl::lts_20220623::internal_any_invocable::LocalManagerNontrivial 4 Fig 0x206616958 absl::lts_20220623::internal_any_invocable::LocalManagerNontrivial 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 24 0 libsystem_kernel.dylib 0x3bbc591cc __psynch_cvwait 1 libsystem_pthread.dylib 0x3e379d6e0 _pthread_cond_wait 2 libc++.1.dylib 0x34a253500 std::__1::condition_variable::wait 3 hermes 0x109064ca8 facebook::jsi::JSError::~JSError 4 hermes 0x109064a5c facebook::jsi::JSError::~JSError 5 libsystem_pthread.dylib 0x3e37a0068 _pthread_start Thread 10 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x000000019bd0d2db x3: 0x0000000303bf74b0 x4: 0x0000000303bf7500 x5: 0x00000002025c10c8 x6: 0x0000000000000012 x7: 0x0000000000000000 x8: 0x000000016b4670e0 x9: 0x000000000000a907 x10: 0x000000009de1d97c x11: 0x0000000000000001 x12: 0x0000000303e8d090 x13: 0x0000000000000000 x14: 0x0000000106f88068 x15: 0x0000000106fabb90 x16: 0x000000030e0f64fc x17: 0x0000000105d506a0 x18: 0x0000000000000000 x19: 0x0000000303e5e700 x20: 0x0000000303e5e700 x21: 0x0000000303e5e700 x22: 0x000000016b4670e0 x23: 0x00000000a1a1a1a1 x24: 0x0f00ffffffffffff x25: 0xa3a3a3a3a3a3a3a3 x26: 0x0000000000000001 x27: 0x00000000211200d5 x28: 0x0000000000000000 fp: 0x000000016b465d10 lr: 0x0000000105fadc54 sp: 0x000000016b465ca0 pc: 0x0000000105fadd48 cpsr: 0x0000000040001000 EOF ```
This is my podfile ```rb require_relative '../node_modules/react-native/scripts/react_native_pods' require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules' platform :ios, '13.0' prepare_react_native_project! # Override Firebase SDK Version $FirebaseSDKVersion = '10.15.0' # The recent version of react-native-firebase require the use of frameworks now # https://rnfirebase.io/#altering-cocoapods-to-use-frameworks use_frameworks! :linkage => :static # Convert all permission pods into static libraries pre_install do |installer| Pod::Installer::Xcode::TargetValidator.send(:define_method, :verify_no_static_framework_transitive_dependencies) {} installer.pod_targets.each do |pod| if pod.name.eql?('RNPermissions') || pod.name.start_with?('Permission-') def pod.build_type; # Uncomment the line corresponding to your CocoaPods version Pod::BuildType.static_library # >= 1.9 # Pod::Target::BuildType.static_library # < 1.9 end end end end # If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set. # because `react-native-flipper` depends on (FlipperKit,...) that will be excluded # # To fix this you can also exclude `react-native-flipper` using a `react-native.config.js` # ```js # module.exports = { # dependencies: { # ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}), # ``` # flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled linkage = ENV['USE_FRAMEWORKS'] if linkage != nil Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green use_frameworks! :linkage => linkage.to_sym end IS_CI = ENV['CI'] target 'Fig' do config = use_native_modules! use_react_native!( :path => config[:reactNativePath], :hermes_enabled => true, :fabric_enabled => false, # Enables Flipper. # # Note that if you have use_frameworks! enabled, Flipper will not work and # you should disable the next line. # :flipper_configuration => flipper_config, # An absolute path to your application root. :app_path => "#{Pod::Config.instance.installation_root}/.." ) target 'FigTests' do inherit! :complete # Pods for testing end post_install do |installer| react_native_post_install( installer, # Set `mac_catalyst_enabled` to `true` in order to apply patches # necessary for Mac Catalyst builds :mac_catalyst_enabled => false ) # if not IS_CI # use_flipper! # end ### START Workaround for running simulator on M1 processor # https://github.com/OneSignal/react-native-onesignal/issues/1103#issuecomment-739543109 installer.pods_project.build_configurations.each do |config| config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64" end ### END: Workaround for running simulator on M1 processor ### START: Workarounds from: https://github.com/facebook/flipper/issues/834#issuecomment-905806177 # Flipper requires a crude patch to bump up iOS deployment target, or "error: thread-local storage is not supported for the current target" # I'm not aware of any other way to fix this one other than bumping iOS deployment target to match react-native (iOS 11 now) installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0' config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO' end end # ...but if you bump iOS deployment target, Flipper barfs again "Time.h:52:17: error: typedef redefinition with different types" # We need to make one crude patch to RCT-Folly - set `__IPHONE_10_0` to our iOS target + 1 # https://github.com/facebook/flipper/issues/834 - 84 comments and still going... `sed -i -e $'s/__IPHONE_10_0/__IPHONE_14_0/' Pods/RCT-Folly/folly/portability/Time.h` ### END workarounds from: https://github.com/facebook/flipper/issues/834#issuecomment-905806177 end # Add permissions: permissions_path = '../node_modules/react-native-permissions/ios' pod 'Permission-Camera', :path => "#{permissions_path}/Camera" # Required for using MLkit barcode scanning in react-native-camera # see: https://github.com/react-native-camera/react-native-camera/blob/master/docs/installation.md#modifying-podfile pod 'react-native-camera', path: '../node_modules/react-native-camera', subspecs: [ 'BarcodeDetectorMLKit' ] pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons' pod 'SuperwallKit', '< 4.0.0' post_integrate do |installer| # This snippet is from https://dev.to/kylefoo/xcode-12-new-build-system-warns-multiple-commands-produce-assets-car-56im # to solve the "multiple commands produce Assets.car" issue that the SuperwallKit Pod introduced # TODO: Find a less hacky solution project_path = './Fig.xcodeproj' project = Xcodeproj::Project.open(project_path) project.targets.each do |target| puts target if target.name == "Fig" phase = target.shell_script_build_phases.find { |bp| bp.name == '[CP] Copy Pods Resources' } if !phase.nil? phase.input_paths.push('${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/Assets.car') phase.output_paths.delete('${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/Assets.car') end end end project.save(project_path) end end target 'OneSignalNotificationServiceExtension' do pod 'OneSignalXCFramework', '>= 5.0', '< 6.0' end ```
MikhailSuendukov commented 1 month ago

I couldn't reproduce this issue. I noticed that there is no CodePush in the crash report, which suggests that the problem might be related to the specific configuration of your application or a corrupted bundle. To further investigate, it would be very helpful if you could provide us with a small demo application that reproduces the error along with detailed steps to reproduce it.

rustygloves commented 1 month ago

We have experienced a similar issue with our app.

I can reproduce it consistently using TestFlight

I install the app, and mandatory update happens. On my next interaction with a React Native text input the app will crash (paste of text or erasing text). It's definitely related to the mandatory update as it no longer happens after a fresh app restart.

Sentry stack trace Screenshot 2024-08-01 at 11 03 07
Podfile ``` # Resolve react_native_pods.rb with node to allow for hoisting def node_require(script) # Resolve script with node to allow for hoisting require Pod::Executable.execute_command('node', ['-p', "require.resolve( '#{script}', {paths: [process.argv[1]]}, )", __dir__]).strip end node_require('react-native/scripts/react_native_pods.rb') node_require('react-native-permissions/scripts/setup.rb') # platform :ios, min_ios_version_supported # uncomment the above line when min_ios_version_supported meets 14.0 as required by plaid platform :ios, 14.0 prepare_react_native_project! # ⬇️ uncomment wanted permissions setup_permissions([ # 'AppTrackingTransparency', # 'Bluetooth', # 'Calendars', # 'CalendarsWriteOnly', # 'Camera', # 'Contacts', # 'FaceID', # 'LocationAccuracy', # 'LocationAlways', # 'LocationWhenInUse', # 'MediaLibrary', # 'Microphone', # 'Motion', 'Notifications', # 'PhotoLibrary', # 'PhotoLibraryAddOnly', # 'Reminders', # 'Siri', # 'SpeechRecognition', # 'StoreKit', ]) #linkage = ENV['USE_FRAMEWORKS'] #if linkage != nil # Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green # use_frameworks! :linkage => linkage.to_sym #end #Beginning with firebase-ios-sdk v9+ (react-native-firebase v15+) you must tell CocoaPods to use frameworks. use_frameworks! :linkage => :static $RNFirebaseAsStaticFramework = true target 'mobile' do # Customer.io SDK for iOS pod 'customerio-reactnative', :path => '../node_modules/customerio-reactnative' pod 'customerio-reactnative/apn', :path => '../node_modules/customerio-reactnative' config = use_native_modules! use_react_native!( :path => config[:reactNativePath], # An absolute path to your application root. :app_path => "#{Pod::Config.instance.installation_root}/.." ) target 'mobileTests' do inherit! :complete # Pods for testing end post_install do |installer| # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202 react_native_post_install( installer, config[:reactNativePath], :mac_catalyst_enabled => false ) end end target 'NotificationServiceExtension' do # Notice the '-richpush' in the line below. This line of code is different from what you added for your main target. pod 'customerio-reactnative-richpush/apn', :path => '../node_modules/customerio-reactnative' end ```

crashes.zip

somasekharkakarla commented 1 month ago

Hi Guys, i also facing crashes after codepush and getting rollbacked. It is mainly happening when we are in some activity(Codepush trigger here). Please look into this. (Mainly in android)

"react-native-code-push": "8.3.1", "react": "18.2.0", "react-native": "0.73.8",

MikhailSuendukov commented 1 month ago

Hi @rustygloves @somasekharkakarla ! I haven't been able to reproduce this error. Mandatory updates are installed successfully without any issues. To help us investigate further, could you please provide a small demo application that reliably reproduces this error, along with detailed steps to replicate the issue?

rustygloves commented 1 month ago

Hi @rustygloves @somasekharkakarla ! I haven't been able to reproduce this error. Mandatory updates are installed successfully without any issues. To help us investigate further, could you please provide a small demo application that reliably reproduces this error, along with detailed steps to replicate the issue?

I will try

IlyaBausovAkvelon commented 3 weeks ago

Closing this issue due to inactivity.

mljlynch commented 2 weeks ago

It feels a little premature to close an issue that is actively waiting for someone to provide a repro.

rustygloves commented 2 weeks ago

It feels a little premature to close an issue that is actively waiting for someone to provide a repro.

I haven't had the time to create one, it's low on my priority list as we are already hoping to move away from code-push anyway. I will open a new issue if I ever get to making a repro