Replacing an existing Swift iOS app with a cross-platform rewrite (same bundle id): will App Store update work and will user data persist? [closed]

We have an iOS app already published on the App Store. The current production app is written natively in Swift.

Now we are rewriting it using a cross-platform framework (React Native). We want to ship the rewritten iOS app as an UPDATE to the same App Store listing (same developer account, same app, same bundle identifier), not as a new app.

Goal:
- Keep the same App Store page and ratings/reviews
- Keep the same bundle identifier
- Ensure existing users keep their local data after updating

Questions:

If we keep the exact same bundle id and sign the app with the same Apple Developer Team, is an App Store update with a completely new codebase (different framework) normally accepted and delivered as a standard update? What are the common pitfalls that can break data persistence for existing users after such a rewrite? Keychain (tokens / credentials) UserDefaults / shared suites Files in app sandbox (Documents/Library) App Groups containers (if used) CoreData/SQLite migrations Do Keychain items created by the old Swift app remain accessible from the new app after update as long as: bundle id stays the same the same Keychain Access Group / entitlements are preserved
Or are there any other constraints? Any App Store Review or App Store Connect restrictions for “replacing” an app with a cross-platform implementation (as long as functionality remains consistent)?

I’m looking for a checklist of what must remain unchanged (bundle id, entitlements, access groups, app group identifiers, etc.) to guarantee a safe update and keep user data.