Post

Replies

Boosts

Views

Activity

Issues with releasing app without iPad support in new Xcode project
Hi everyone This is a continuation of thread 795594 We have recently decided to bring iOS development in-house from a consulting firm and have developed a completely new codebase for our existing app in a new Xcode project based on SwiftUI. We have ensured that the bundleId is the same as in the old project. We are using Xcode version 16.0, and when we try to release the new version to the App Store, we encounter an error stating that the old Xcode project had destination support for iPad, but the new project does not. We do not wish to release this version for iPad, but we are unsure how to bypass this error. Is there anyone who has experience with this issue or can provide us with advice on how to handle it? We would greatly appreciate any help or insights.
0
0
55
Aug ’25
New App taking over Bundle Id from old app.
Hi everyone We have brought the iOS development in-house from a consulting firm and have developed a new app that will replace the old one. To minimize disruption for users of the old app during this upgrade, we would like to release the new app as an update to the old one, using the Bundle ID from the old app. It is important to note that the old app has already been released through the App Store. The two apps share no code and are almost incompatible on any points. Is it possible to change the Bundle ID and delete UserDefaults from the old app during the transition to the new app? We look forward to your input!
4
0
127
Aug ’25