“build disappears”

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.

Hi everyone, We recently submitted an update for our existing iOS application and just wanted to verify that everything looks correct on our side in App Store Connect. The previous version of the app was approved and is currently live on the App Store. This new submission is a small update that improves some UI elements and adds minor usability improvements for our customers. At the moment the build is still waiting for review, and since we are coordinating this update with our client rollout schedule, we wanted to confirm that there are no issues with the submission metadata or the selected build. If anyone from the App Review team happens to see this and can confirm that the submission looks complete, we would really appreciate it. App ID: 6759172913 Thank you very much for your time and support. Kind regards, José Rodríguez

Hello, I received a Guideline 1.2 compliance notice for my app OMG: Video Chat (Apple ID: 6756574665) on March 7, 2026, with a 14-day deadline to submit a compliant update. The issues raised in the notice — random matching and anonymous chat — were already resolved in the current live version of the app prior to receiving the notice. Specifically: Random matching has been completely removed. Users browse profiles and choose who to connect with. All calls require mutual consent via Accept/Decline. Sign in with Apple is mandatory — no anonymous or guest access exists. Selfie-based age verification is active. Full moderation system is in place: content filtering, user reporting, blocking, and 24/7 monitoring. I responded to the notice on March 7 with a detailed explanation, screen recording, and screenshots demonstrating the current app flow. I also submitted a compliant build and requested an expedited review. As of today (March 12), I have received no acknowledgment, no feedback, and the build

All of my notarization submissions have been stuck at In Progress for over a week. I have 6 submissions spanning from March 4 to March 10, 2026, and none of them have completed or returned any errors. Affected submissions: 685708f6 — MeetingRecorder-1.5.0.dmg (submitted Mar 10) — In Progress 6ade1490 — MeetingRecorder-1.5.0.dmg (submitted Mar 10) — In Progress 99d39bd0 — MeetingRecorder-1.4.12.dmg (submitted Mar 6) — In Progress e65f95e1 — MeetingRecorder-1.4.9.dmg (submitted Mar 6) — In Progress eb51b220 — MeetingRecorder-1.4.9.dmg (submitted Mar 5) — In Progress 9cc33cfd — MeetingRecorder-1.4.9.dmg (submitted Mar 4) — In Progress Running notarytool log returns Submission log is not yet available. Team ID: HXVLV4P425 The app is a macOS menu bar application for meeting recording and transcription. It is signed with a valid Developer ID certificate and has been built with hardened runtime enabled. I've tried resubmitting multiple times across different builds (1.4.9, 1.4.12, 1.5.0), but all submission

There is a long-standing, structural issue with the iPadOS Korean IME when using a hardware keyboard. The IME forcibly intercepts the (quote) keydown event and injects Unicode smart/curved quotes (“ or ”) directly into the text field. This hardcoded behavior ignores both: User Settings: The global Smart Punctuation toggle in [Settings > General > Keyboard] is completely ignored. Developer APIs: Setting UITextInputTraits.smartQuotesType = .no on a UITextView or UITextField has absolutely no effect when the Korean keyboard is active. Steps to Reproduce: Set smartQuotesType = .no on a standard UITextView. Connect a hardware keyboard. Switch input language to English -> Press the quote key. (Result: ASCII straight quote - Correct behavior) Switch input language to Korean -> Press the quote key. (Result: Unicode curved quote “ - Incorrect behavior) Impact on Developers & Users: Because the OS IME forcefully injects the curved Unicode character before the app can process the raw key event, develop

There is a long-standing, structural issue with the iPadOS Korean IME when using a hardware keyboard. The IME forcibly intercepts the (quote) keydown event and injects Unicode smart/curved quotes (“ or ”) directly into the text field. This hardcoded behavior ignores both: User Settings: The global Smart Punctuation toggle in [Settings > General > Keyboard] is completely ignored. Developer APIs: Setting UITextInputTraits.smartQuotesType = .no on a UITextView or UITextField has absolutely no effect when the Korean keyboard is active. Steps to Reproduce: Set smartQuotesType = .no on a standard UITextView. Connect a hardware keyboard. Switch input language to English -> Press the quote key. (Result: ASCII straight quote - Correct behavior) Switch input language to Korean -> Press the quote key. (Result: Unicode curved quote “ - Incorrect behavior) Impact on Developers & Users: Because the OS IME forcefully injects the curved Unicode character before the app can process the raw key event, develop

Hello everyone, I wanted to check whether other developers are currently experiencing unusually long “Waiting for Review” times. Our app Aslan Wealth (App ID: 6755077470) has been stuck in Waiting for Review for quite a while and has never entered the “In Review” stage. Timeline Feb 18, 2026 – Version submitted for review Feb 23 – Contacted Apple Developer Support regarding review status Feb 24 – Received reply that the case was escalated to the review team Mar 3 – Still in Waiting for Review (confirmed by support that the app is still in the queue) Mar 7–11 – Followed up with Developer Support again Mar 12 – Still Waiting for Review So the app has now been waiting for review for more than 3 weeks without ever entering active review. Additional information All agreements are active No messages in Resolution Center Build was not modified after submission App status remains Waiting for Review Questions Has anyone else recently experienced similar multi-week delays in the “Waiting for Review” stage? If

Hello everyone, I would like to ask if other developers are currently experiencing unusually long App Review delays for new apps. Here is my timeline for this app (Apple ID: 6758083858): Jan 22, 2026: Initial build submitted Jan 22 – Mar 7, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 7, 2026: Cancelled and resubmitted a new build Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent follow-up emails regarding the delay Contacted Apple support by phone and asked them to leave a message for the App Review team Each time I was told that the situation would be checked or that the review team would look into it. However, it has now been about two weeks since my last contact and there has been no update or progress. While browsing the Developer Forums, I also noticed that many recent posts seem to des

Hello everyone, I wanted to check whether other developers have recently experienced unusually long “Waiting for Review” times. Our current submission timeline looks like this: Timeline Feb 14, 2026 – Initial build submitted Feb 14 – Present – Status has remained “Waiting for Review” (never entered “In Review”) Feb 18–19 – Contacted App Review support Feb 24 – Received reply that the case was escalated / expedited Feb 26 – Mar 9 – Continued communication with support; each time they confirmed the app is still in the queue and that they contacted the review team Mar 12 – Still Waiting for Review So as of now, the build has been waiting for review for nearly four weeks without ever entering active review. I’m trying to understand whether this is an isolated case or if others are seeing similar delays recently. Questions: Has anyone else experienced multi-week “Waiting for Review” delays recently? If you had a similar situation, did you eventually receive any explanation from the review team? A

Hello, We are experiencing repeated notarization delays for our macOS app distributed outside the Mac App Store. Current submission ID: 45d7cac0-bd8a-4d48-b886-1cad7649adf4 Previous affected submission ID: ff61de1e-15f5-4bbe-8b34-a91a6f73b978 Issue description: xcrun notarytool submit succeeds and returns a submission ID. xcrun notarytool info keeps returning In Progress for a very long time. In the current case, the submission has remained In Progress for more than 45 minutes. This issue has happened repeatedly across multiple submissions. What we have already checked: We are not using a local proxy for notarization requests. We separated submit and polling in our build script to verify the exact stage. We retried multiple times. We reduced package contents to rule out newly introduced app content. Could someone from Apple please help check whether these submission IDs are stuck in the notarization pipeline, or advise what additional diagnostics we should provide? Thank you.