[iOS] Code push back initial release after update ios version

[amdrade]

The app was working correctly with codepush, after updating the iOS version 16.7.7 to 16.7.8, the app returns to the initial version from when it was published in the apple store. When generating a new release, the app updates normally.

Steps to Reproduce Release an update Close / reopen the app Update iOS version

Expected Behavior App should load the updated bundle

Actual Behavior What actually happens? The app returns to the initial version from when it was published in the apple store and load the binary bundle.

Environment react-native-code-push version: 7.0.1 react-native version: 0.65.3 iOS/Android/Windows version: iOS 16.8 Does this reproduce on a debug build or release build? release Does this reproduce on a simulator, or only on a physical device? physical device

[tiendnvietis]

Ensure that you configure your release scheme with the correct values. To verify this, navigate to Build Settings and locate Apple Clang - Preprocessing. Check the Preprocessor Macros section. Confirm that the DEBUG=1 macro is not set for your release scheme (typically the default 'Release' scheme or any custom scheme you have created). .

[amdrade]

Configuration is OK

[DordeDimitrijev]

Hi @amdrade thank you for reaching out. Please make sure your Appdelage.m implementation is as stated in the docs

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [CodePush bundleURL];
#endif
}

If everything is set according to the docs it'd be great if you could share a small demo app which can be used to reproduce this issue.

Could you confirm whether the rollbacks are occurring exclusively on iOS updates, if so does it only happen for updates from 16.7.7 to 16.7.8 or for all IOS device updates?

[DordeDimitrijev]

Closing due inactivity.

[amdrade]

Appdelage.m its OK

[DordeDimitrijev]

Could you please share a demo app since I am unable to reproduce this issue, if not could you share logs?