“build disappears”

Hi everyone, I’m running into a recurring issue when submitting my app to the App Store. The app is made with Unity and contains a single non-consumable IAP. Said IAP works fine locally, and sandbox testing with Xcode works when we test the build internally. Here is the current behaviour: On Game launch, the paywall pop-up displays correctly, I can try to purchase the bonus content. I go through the whole mock payment process, it takes a little while to validate but it does go through. It asks me to “pay” a second time (as if the first one hadn’t been taken into account), there’s a bit of loading but the payment is validated. A pop-up tells me it’s confirmed. Back in game, the content is correctly unlocked and accessible. But during App Store review, the reviewers report that the in-app purchase button is unresponsive. The purchase cannot be initiated, and an error that says Cannot initiate purchase because product was not found or simply failing to start. Here’s what I’ve confirmed so far: The IAP p

I've recently installed 26.1 Beta 3 alongside stable 26.0.1 When building my app with 26.0.1 the final .ipa size is ~17mb, however after building my app with 26.1 Beta 3 the size has increased up to ~22mb The main difference is Assets.car blowing from 1.1mb to 5.6mb (or 8.6mb if I include all icons settings). Upon examining I've found new liquid glass .icon file duplicating itself multiple times as png variants (any, dark, tinted, etc). Is anyone else experiencing this issue?

With agentic coding and AI rapidly improving at solving development problems, I’m starting to question what the next three to five years will look like for iOS developers and whether manual coding will gradually disappear. I’ve been building iOS apps full time since 2013 and while I appreciate AI for speeding up workflows like unit testing, I worry that over reliance could weaken our core skills, reduce our understanding of evolving APIs, and ultimately impact our long term value and demand in the industry, does anyone else feel the same?

So I'm reworking couple things in my app. And I noticed I had this old code that does the following: Creates a temporary directory. Writes a file in the temporary directory. After the file is written moves the file out of the temporary location and places it in its final destination. Okay so I was not creating the temporary directory using the recommended API. I was simply doing something like this: NSURL *tempDirectory = [NSURL fileURLWithPath:[NSTemporaryDirectory() stringByAppendingPathComponent:[NSProcessInfo processInfo].globallyUniqueString]]; // Create tempDirectory and write files inside it. Now I just changed the code to use the recommended API which takes the the volume of the target destination into account: -URLForDirectory:inDomain:appropriateForURL:create:error:) and I pass in NSItemReplacementDirectory and a url to appropriateForURL so the destination volume is taken into account. Now I have external storage mounted and I use the recommended approach. I discovered NSFileManager simply writes a

I’m sharing my situation in case others have experienced something similar. I initially submitted my app for review on February 4, and it remained in “Waiting for Review” for over 12 days without any feedback or request for additional information. I also sent a message through App Store Connect on February 11, but did not receive a response. To help move things forward, I’ve now resubmitted an updated build with clearer onboarding, improved permission explanations, and some minor UI improvements. I included detailed notes for the reviewer explaining the changes. I’m staying patient and cooperative, but I wanted to ask if others have encountered similar delays recently, and whether resubmitting helped unblock the review. Thanks in advance for any insights 🙂

We recently changed the development team for our app and are getting ready for the first update since the change. We store a small amount of data in an sqlite database. From what I understand that data should be retained for users when updating the app version since the Bundle ID has remained the same. When I update the app from the currently released App Store build, which was from the old development team, to the latest build in TestFlight the data is not being retained. Is there something else that needs to be done to retain the data? Is it possible that the data is only being lost when updating from TestFlight but will be retained when updating the app from the App Store?

I've submitted multiple builds to Testflight over the course of a week and all of them as stuck in a Processing state. Some extending almost a week at this point. Unfortunately I can't clear these, can't delete the app and restart the submission entirely, or anything else. Any pointers would be greatly appreciated, at this point I'm assuming something internal to Testflight is hosed.