“build disappears”

Hello, I have an internal TestFlight build for my app PewPewApp (Apple ID 6760741808). The build is processed, assigned to an internal group, and the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. However, installation from TestFlight fails with: “The requested app is not available or doesn’t exist.” Could you please check whether there is an account-level or backend TestFlight distribution issue affecting this app/build? Thank you.

Im a Quality Engineer and using Appium to automate in Physical devices so installed appium server and xcuitest. We need to build the webdriveragent project from xcode , when doing that getting the following error Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/ I have a apple account licensed but still unable to resolve this, any immediate help is highly appreciated

Hello, My app Zen Mahjong! has been stuck in the App Review process for an unusually long time and I’m trying to understand if something might be wrong with the submission. Timeline: First submission entered “In Review” and stayed there for 6 days without a decision. I rejected that build, uploaded a new build and resubmitted on February 17. Since then the app has been in “Waiting for Review” for more than 3 weeks. Additional context: App size ~40 MB Only IAP is a “Remove Ads” purchase I already contacted Developer Support and opened an expedited review request. Support also mentioned that this delay seems unusual. Has anyone experienced something similar or could this indicate that the submission is stuck in the review pipeline? Any guidance would be greatly appreciated. Thank you.

Hi everyone, I’m looking for some guidance regarding my app review process. I submitted my iOS app (version 1.0) and it has been in “Waiting for Review” status for quite some time now. I understand that review times can vary, but this is taking longer than I expected, and I’m not sure if this is normal or if there might be an issue with my submission. For some additional context: The first time I submitted the app, it was rejected. Since I’m new to the Apple Developer platform, I mistakenly removed the rejected build instead of addressing the rejection and resubmitting. After that, I submitted the app again, and now it’s been waiting for review. My question is: Could removing the rejected build have caused any delays or issues with the review process? Or is the current waiting time unrelated to that? I would really appreciate any advice from experienced developers on whether I should just continue waiting or if there’s something specific I should check or do. Thank you in advance for your he

I’m following up regarding two apps I submitted on March 2 that are still stuck in “Waiting for Review.” First app id is 6759584758 and second is 6759892034 It has now been over two weeks with no movement or communication. This is already beyond the typical review timeframe Apple communicates, and it’s starting to seriously impact my ability to launch and operate my apps. After waiting this long, I contacted support directly. During that call, I was told that my apps would be added for expedited review. However, even after that step, there has still been no progress or update. At this point, the situation is becoming increasingly frustrating due to: No visibility into what’s causing the delay No estimated timeline No follow-through after being told the apps would be expedited As a paying Apple Developer, I depend on a reasonable and predictable review process. These delays directly affect my ability to plan launches, marketing, and monetization — especially as an independent developer. I’m not asking to bypas

CloudKit: Efficient way to get user's rank in leaderboard without fetching all records? I'm building a leaderboard feature using CloudKit's public database and need advice on the best approach to calculate a user's rank efficiently. Current Setup Record Structure: Record Type: LeaderboardScore Fields: period (String): daily, weekly, monthly, allTime score (Int): User's score profile (Reference): Link to user's profile achievedAt (Date): Timestamp Leaderboard Display: Initially fetch first 15 users (sorted by score descending) Paginate to load more as user scrolls Show total player count Show current user's rank (even if not in top 15) The Challenge I can fetch the first 15 users easily with a sorted query, but I need to display the current user's rank regardless of their position. For example: User could be ranked #1 (in top 15) ✅ Easy User could be ranked #247 (not in top 15) ❌ How to get this efficiently? My Current Approach Query records with scores higher than the user's score and count them: //

Dear Apple Support, I would like to raise a concern regarding the behavior of the “Desktop & Documents Folders” feature in iCloud Drive. From a business and development standpoint, the fact that folders may be automatically moved or created without clear and explicit user awareness is quite concerning. File system behavior is something users generally expect to remain predictable and fully under their control. In particular, when working in development environments, even small and unintended changes to folder structures can lead to issues such as broken file paths, build errors, or inconsistencies in project setups. The possibility that such changes may occur automatically introduces an element of uncertainty that is difficult to manage in professional workflows. Additionally, there are security considerations. For example, if sensitive files such as configuration data or API keys are temporarily stored on the Desktop, the possibility that they could be unintentionally synced to the cloud raises

[Submitted as FB22226720] For a NavigationStack destination, applying .navigationBarBackButtonHidden(true) hides the back button and also disables the interactive left-edge back gesture when using the standard push navigation transition. However, when the destination uses .navigationTransition(.zoom), the back button is hidden but the left-edge back gesture is still available—it can still be dismissed even though back is intentionally suppressed. This creates inconsistent behavior between navigation transition styles. navigationBarBackButtonHidden(_:) works with a standard push transition, but not with .navigationTransition(.zoom). In the code below, .interactiveDismissDisabled(true) is also applied as another attempt to suppress the back-swipe gesture, but it has no effect. As a result, there’s currently no clean way to prevent back navigation when using the zoom transition. REPRO STEPS Create an iOS project then replace ContentView with code below, build and run. Leave nav type set to List Push. Op

I've got a Project with a bunch of frameworks, each of which has a static library version of itself (for compiling command-line tools that also use the code). Compiling the frameworks goes fine. Compiling one of the static libraries (A Mime-parsing framework) is giving me the rather odd message that a bunch of symbols are ambiguous, but the ambiguity resolves to the same symbol in the error-message... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:57:18: error: reference to 'E3_SMIME_ENVELOPED_DATA' is ambiguous 57 | case E3_SMIME_ENVELOPED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppP

When creating an icon using icon composer, I cant upload a build to testflight/App Store connect. Running on device from Xcode works fine, but as soon as I archive and upload to App Store Connect, I get an error saying the icon contains an alpha channel

Sharing a solution for a problem that took me a while to figure out. Problem: During development of a macOS 26 app that uses ScreenCaptureKit, the screen capture permissions were being reset after every build. Each time I compiled and ran the app from Xcode, I had to re-authorize screen capture in System Settings. CGPreflightScreenCaptureAccess() would return false even though I'd just granted permission minutes ago. Root cause: I was using ad-hoc code signing during development. macOS ties screen capture permissions to the app's code signing identity. With ad-hoc signing, the identity changes on every build, so the system treats each build as a new app. Solution: Switch to an Apple Development certificate for debug builds. In Xcode: Build Settings → Code Signing Identity → Debug → set to Apple Development Make sure your development team is selected After this change, the signing identity remains stable across builds, and screen capture permissions persist

Hello everyone, I’m currently experiencing unusually long wait times for app reviews and wanted to check if others are seeing similar delays this week. Here is the current status of my submissions: App Store Update: Stuck in Waiting for Review much longer than the typical 24–48 hour window. New Version: A newly submitted version also seems to be stalled in the initial phase. TestFlight Processing: Even TestFlight builds are taking longer than usual to process. Expedited Review: I've attempted an expedited review request and direct communication, but the status remains unchanged so far. What’s confusing is that I see other apps in the same category receiving updates, so I’m unsure if this is a localized technical glitch or a broader delay affecting a specific group of developers. I’m not looking to escalate anything just yet; I’m simply trying to gauge if this is a widespread issue at the moment. I would greatly appreciate any insights into your recent experiences or if you've noticed similar patterns