“build disappears”

Hi Writing an app in Swift on Xcode for my iPhone, all software is the latest version. If after making a minor change and re-building all the application data has disappeared, is there a way to see if it is still in the .modelContainer and just not showing up?

Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬

When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new SwiftUI App project using Xcode 26.3. Leave all project settings at defaul

While Apple prides itself on providing the ultimate experience for both users and developers, many find themselves trapped in a technical black hole with no exit. The issue isn't just the complexity of the systems, but the sheer inability of these systems to handle a developer’s most basic need: accessing their account to manage their business. The Dead-End Loop: Too Many Verification Codes The disaster begins with a seemingly harmless but business-destroying message: You have sent too many verification codes. Please try again later. At this point, Apple’s system—with its supposed intelligence—decides to freeze your account for two days or more. You wait patiently, return after 48 hours to log in, only to be met by the exact same message. This isn’t security; it’s primitive technical failure. How can a company of Apple’s magnitude fail to program a smart system that distinguishes between a breach attempt and a developer trying to access their work tools? Persistent failure for over a month without a root solu

Hello everyone, I’m experiencing an issue with the review process for my app on App Store Connect. My app has been stuck in “Waiting for Review” for over 30 days, and the review process has not started yet. Initially, I submitted the build on February 9, but the status remained “Waiting for Review” for a long time and never moved to “In Review.” Because of this, I canceled the submission and resubmitted the build on February 17. However, even after resubmitting, the app is still stuck in “Waiting for Review.” I also submitted a request for an expedited review, but unfortunately I have not received any response regarding that request either. Since the app status is still “Waiting for Review,” the Resolution Center option is not available yet, so I cannot contact the App Review team directly from there. I also attempted to contact Apple Developer Support but have not received a response yet. Has anyone experienced a similar situation where the app remained in “Waiting for Review” for this long

Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

Hi, writing a database app for storing equipment details. Spent the day doing minor changes and tidying with many backups made, and always re-building to check its all working. Everything ok but then next build looses all data, what's the best thing to check to see if the data is still there, any help would be fantastic.

I'm just looking for help/guidance on what if something I did wrong in my build submission? The first test flight build I submitted went through in about 1 day, 2 build updates after that went through and were deployed for my test flight participants each in less than 24 hours. The last build I have submitted has been 6 days now. I have had to submitted multiple builds and cancel a few of them as I keep making progress on my app. I have submitted a ticket for assistance, and called the help number. Thank you in advance for any help. I appreciate the community.