Absolutely—Apple has no problem accepting a fully rewritten iOS app that uses the same Bundle ID as your existing React Native-based app. This is a super common move for teams looking to switch from cross-platform to native Swift, so here’s what you need to keep in mind to make the process smooth:

What You Need to Know Up Front #

• Bundle ID is your app’s unique fingerprint：Apple uses the Bundle ID to identify your app, full stop—your tech stack doesn’t factor into that. As long as you’re submitting from the same Apple Developer Account that owns the original Bundle ID, the App Store will see this as an update to your existing app, not a brand new one.
• Submission is just like a regular update：When you’re ready to launch the Swift version, upload it as a new build in App Store Connect exactly how you’d push a normal update. Feel free to mention the full rewrite in your release notes (e.g., "Fully rebuilt with native Swift for faster performance!")—Apple doesn’t have any issue with that.
• Apple cares about guidelines, not your tech stack：The review team only checks if your app meets their App Store Guidelines (privacy rules, content policies, functionality, etc.). They won’t reject your app just because you switched from React Native to Swift—focus on making sure your new app follows the rules, and you’ll be good to go.

Critical Prep Steps to Avoid Headaches #

• Don’t drop core features：While Apple doesn’t enforce this, make sure your Swift app has at least all the key features your users rely on from the React Native version. Losing functionality after an update will lead to frustrated users and bad reviews, even if it doesn’t get your app rejected.
• Match permission configurations：Double-check your new app’s Info.plist file to make sure it includes all the same permission descriptions (for camera, location, notifications, etc.) that the original app used—if those features are still present. Missing these descriptions is one of the most common reasons for review delays.
• Plan for data migration：If your original app stores user data locally (like React Native’s AsyncStorage), build a way to migrate that data to your Swift app’s storage (like UserDefaults or Core Data). This is huge for user trust—even though Apple won’t audit this specifically, losing user data will tank your app’s reputation.

Real-World Context #

Lots of development teams have made this exact transition—from React Native to Swift, or even from Objective-C to Swift—using the same Bundle ID, and their updates were approved without a hitch. The biggest thing is to treat this like a standard app update, not a new app submission.

内容的提问来源于stack exchange，提问作者Jacobo Koenig