Overview

Hello Everyone, I have published my app few months back . The app does not show up in search when I search with the app name . It's a social media app and i provided the right key words . FYI- But when I search the app with combining the company name and app name it shows up. I am in contact with apple support for last 1 month and all the time , i get the an answer that the engineers are woking on it. They even suggested me to include the app name in the Key words, which I did , but no results. Today the supervisor suggests that support team might not be able to do much and I have to revisit my settings. I don't know what else to change other than the key words. . He also highlighted that since Language EN was chosen and the my app name is not an english word, could be also the reason for it not showing up in the search. Can someone please help to provide a solution to this.

Title says it all. I type a colon when Xcode is set to Vim mode, and for some reason the line number pop-up comes up, as if I'd typed Command-L. Why is that? I feel like it didn't do this in the past; I could have sworn I used to be able to close editor tabs by typing :x. At any rate, this is incorrect behavior; jumping to line numbers in vim is done by just typing the number followed by a capital G. Is there any way to turn this off? I couldn't find anything in the shortcuts preferences.

Our app's auto-renewable subscription (Product ID: istanbul.membership.monthly, Bundle ID: com.mehmetozenen.ustaistanbulapp) has been returning zero products from Product.products(for:) since August 24, 2026, blocking 100% of new iOS subscriptions on our live production app. Verified correct on our side: Subscription status: Approved Paid Applications Agreement: Active (continuously since Feb 2026, no gaps) Territory pricing: set, including Turkey Product ID matches exactly, correct app No changes to Agreements/Tax/Banking around the failure date Steps to reproduce: Call Product.products(for:) (or via react-native-iap's fetchProducts) with SKU istanbul.membership.monthly, type auto-renewable subscription. Result: empty product array, no error thrown. Purchase sheet never appears since there is no product to purchase. Reproduced on: 4+ independent physical iOS devices Multiple different Apple IDs Both Sandbox and Production StoreKit environments (identical failure in both) Both Wi-Fi and cellular networks A historical app build (from before Aug 24) that was never modified and worked correctly as recently as Aug 23 — ruling out any client-side code cause This same product worked correctly as recently as 2026-08-23 (server-side purchase verification log confirms a real successful transaction that day). It broke starting 2026-08-24, with no corresponding change on our end. I've already opened a Developer Technical Support case (Case-ID 21790415) and submitted a full sysdiagnose with reproduction timestamps, but have not received a substantive update in over a week. Posting here in case others have hit the same regression, or in case anyone from Apple can help escalate. Has anyone else seen Product.products(for:) / fetchProducts silently returning empty for an otherwise valid, Approved auto-renewable subscription starting around late August 2026?

Hello, I'm stuck in the middle of my Apple Developer Program enrollment and cannot move forward or backward. Timeline: About two weeks ago I enrolled via developer.apple.com/programs/enroll and my card was charged the full membership fee ($143.95 CAD). Shortly after, I received an email from Apple asking me to verify my address details (my Apple Account previously had an old address in a different country; I updated it to my current Canadian address the same day). The email contains a link to upload verification documents. That link leads to developer.apple.com/contact/ (File Upload), which shows: "Sorry, you don't have access. Your account isn't authorized to upload files." — so I physically cannot submit the documents Apple is asking for. Tried multiple browsers and devices, same result. I am signed in with the same Apple Account I used for enrollment. Enrollment through the Apple Developer app is also unavailable: the Enroll Now button is disabled with the message "Enrollment through the Apple Developer app is not available for this Apple Account" — presumably because of the pending web enrollment. I have submitted 4 support requests through the contact form over the past two weeks. No reply to any of them. A phone call to general Apple support did not help either. So: I was charged, I cannot complete verification because the upload page rejects my account, and I cannot re-enroll because the pending enrollment blocks the app flow. Could someone from Apple please authorize my account for the document upload so I can complete verification and activate my enrollment? Case numbers from my support requests: 102930512720 and 102924505342 Thank you.

We have a monthly subscription and an annual subscription with a 3-day free trial. The monthly converts fine. On the annual, trials tend to enter billing retry rather than convert — users don't cancel, the charge just fails. We've audited our implementation and found nothing on our side that participates in the renewal charge. What can a developer actually do about this? Does trial length, price point, or using a paid introductory offer instead of a free trial make a difference?

My app review is taking so much longer than it usually does and it hasn't even reached the review state. It just says "Waiting for review" I requested expedited and sat on hold for 2 hours and ultimately chose to hang up. Not sure why this is and the whole purpose of expedited review is to ensure crucial updates get pushes and it feels useless when an update I need pushed out is being ignored for review.

macOS Tahoe appears to ignore /etc/fstab ro and noauto — findings and workaround I encountered what appears to be a regression in macOS Tahoe where Disk Arbitration no longer honors ro and noauto policies in /etc/fstab for external volumes. I am posting my findings here both to see whether others can reproduce the issue and to document a workaround, particularly for anyone using macOS for disk recovery or other workflows where preventing writes is important. The problem A configuration such as: UUID= none exfat noauto does not prevent the volume from automatically mounting. Similarly: UUID= none exfat ro does not result in a read-only mount. I also tested: UUID= none exfat ro,noauto with the same problem. This configuration worked for me before upgrading from macOS Sequoia to Tahoe. I initially suspected this might be related to Tahoe's newer exFAT/FSKit path, but testing APFS produced the same general behavior. It therefore appears to be broader than exFAT alone. /etc/fstab itself is being parsed correctly I tested the libc fstab interface using getfsent(). For example, an entry containing noauto is returned as: spec=UUID= | file=none | vfstype=exfat | mntops=noauto | type=rw So this does not appear to be a simple malformed-fstab problem. Tracing also shows diskarbitrationd accessing /etc/fstab. What Disk Arbitration is doing Unified logs from an affected exFAT mount show the filesystem being successfully probed, followed by Disk Arbitration mount approval callbacks. After approval, the reported mount options are: Mount options nodev,noowners,nosuid and the volume is then mounted successfully. The ro policy expected from /etc/fstab is notably absent from those mount options. Direct read-only mounting still works The filesystem itself is capable of being mounted read-only. For example, for exFAT: sudo mkdir -p /Volumes/Exchange sudo mount_exfat -o rdonly /dev/diskXsY /Volumes/Exchange This produces a genuinely read-only filesystem; a write test fails as expected. So at least in my testing, the problem appears to be associated with the normal Disk Arbitration mounting path rather than an inability of the filesystem to support read-only mounting. A working noauto workaround Disk Arbitration still supports mount approval callbacks. I tested a small client using: DAApprovalSessionCreate DARegisterDiskMountApprovalCallback DADissenterCreate The callback checks the volume UUID against /etc/fstab. If the corresponding entry contains noauto, it returns: kDAReturnNotPermitted This successfully prevents the volume from mounting. The test output looks like: [BLOCK] mount request: /dev/disk5s1 [BLOCK] mount request: /dev/disk5s2 The volume remains unmounted. Interestingly, this also blocks: diskutil mount /dev/diskXsY because diskutil mount goes through Disk Arbitration. A direct filesystem mount such as mount_exfat, however, bypasses that approval request and can still be used to deliberately mount the filesystem read-only. Why this matters For an ordinary external disk, an unexpected automount may only be annoying. For data recovery, forensic inspection, or a failing disk, the difference can be important. If /etc/fstab says: ro I expect that policy to protect the source filesystem from writes. Silently mounting the filesystem read-write instead means that the volume becomes available to Finder and other background services. That is exactly what I am trying to avoid when working with a recovery source. For this reason, I would recommend verifying the actual mount state rather than assuming that an existing /etc/fstab ro entry is still protecting a disk after upgrading to Tahoe. For example: mount or: diskutil info /dev/diskXsY should be used to confirm the resulting state. Current workaround design I am currently using a small compatibility helper that treats /etc/fstab as the source of truth: /etc/fstab ↓ compatibility helper ↓ Disk Arbitration mount approval The daemon side handles mount policy before Disk Arbitration can automatically mount the volume. An explicit mount helper can then perform a direct filesystem mount with the options specified in /etc/fstab, including read-only mounting where required. The intention is not to replace /etc/fstab, but to restore the behavior that was previously provided by the system. Reproduction request If anyone else is running macOS Tahoe, I would be interested to know whether you can reproduce this with either: UUID= none apfs noauto or: UUID= none exfat noauto and similarly with ro. Please be careful when testing ro: use a disposable/test volume rather than a disk whose contents actually depend on remaining read-only. I have also submitted this to Apple through Feedback Assistant. Feedback ID: 24677522 I will update this post if Apple provides additional information or if a later Tahoe update changes the behavior.

Hi everyone, I’m looking for external TestFlight testers for Personal Finance, a SwiftUI app for managing accounts, payment cards, investments, and personal budgets in one place. The app does not connect to banks. Users enter and manage their financial information manually, and the data remains on the device. The current beta includes: • Account, card, and investment balance tracking • Personal budget calculations with recurring and one-time items • Automatic balance updates for card payments • Home Screen widgets for balances and budgets • Direct links from widgets to the relevant editing views • Optimized layouts for both iPhone and iPad • Finnish and English language support I would especially appreciate feedback on: • Overall usability and clarity • Calculation accuracy • Adding and editing financial information • Widget installation and behavior • iPad layouts in portrait, landscape, and Split View • Missing features or confusing workflows • Crashes, data issues, and visual bugs Public TestFlight link: https://testflight.apple.com/join/BZgZNnhn Feedback can be submitted directly through TestFlight. Thank you to anyone willing to try it and share their experience.

Contact Airtel 09262—81—2308. immediately, provide the wrong and correct numbers along with the complete transaction details, and ask support to check whether the particular recharge can be reversed or otherwise resolved. Avoid making another payment until you have confirmed the status of the original recharge.

Summary A SpotLightComponent with SpotLightComponent.SurroundingsLight() (and a ProjectiveTexture) lights the flat part of my ceiling and the walls, but never the two sloped ceiling surfaces of a converted attic room, at any angle, intensity, attenuation radius or falloff. The lit area stops in a hard straight line exactly where the flat ceiling meets each slope, even though the beam clearly extends past that line. The sloped surfaces are fully present in SceneReconstructionProvider's mesh, and their faces point into the room. So this doesn't look like a scene understanding coverage problem. It looks as if physical space lighting only considers surfaces classified as horizontal ceiling, wall or floor, and skips slanted ones. Steps to reproduce Open a mixed immersive space in a room with a sloped ceiling (a converted attic, or any vaulted ceiling). Add an entity with SpotLightComponent(color: .white, intensity: 40_000, innerAngleInDegrees: 44.5, outerAngleInDegrees: 45, attenuationRadius: 10), SpotLightComponent.SurroundingsLight(), and a SpotLightComponent.ProjectiveTexture carrying a labelled grid texture so the beam's extent is visible. Place it near the floor under the wearer and aim it straight up. Run SceneReconstructionProvider alongside and draw each MeshAnchor as a wireframe (or as a solid material with faceCulling = .back) to confirm the mesh covers the slopes and faces inward. Expected The projected pattern conforms to every surface in the scene understanding mesh inside the cone, including the sloped ceiling, as it does for the flat ceiling and walls. Actual The pattern appears only on the flat ceiling strip and on the walls. Both slopes stay completely dark, with a hard straight cut at the crease. Tilting the light to aim directly at a slope, raising intensity to 200,000, and changing attenuation radius and falloff make no difference. The wireframe shows continuous mesh across the crease and onto the slopes; the back-face-culled solid view shows the slope faces pointing into the room. Screenshots attached: (1) the projected grid stopping at the crease, (2) the reconstruction wireframe covering the slopes, (3) the solid front-faces-only mesh showing the slopes are front-facing. (4) an additional image of the projected grid with both ceiling and walls in view Code let spot = Entity() spot.components.set(SpotLightComponent.SurroundingsLight()) var light = SpotLightComponent(color: .white, intensity: 40_000, innerAngleInDegrees: 44.5, outerAngleInDegrees: 45, attenuationRadius: 10) light.attenuationFalloffExponent = 0.5 spot.components.set(light) spot.components.set(SpotLightComponent.ProjectiveTexture(texture: gridTexture)) spot.look(at: from + SIMD3(0, 1, 0), from: from, upVector: SIMD3(0, 0, -1), relativeTo: nil) root.addChild(spot) Questions Is physical space lighting limited to horizontally and vertically classified surfaces by design? If so, could this be documented on SurroundingsLight, and is there a way to include slanted surfaces? If not by design, is there anything an app can do to have the light use the full reconstruction mesh?

There’s an item named “HOOGLES” with a cartoon bear in my iMessage apps settings under “Only in Messages. I’d like to know what it is

I have a non-consummable in-app purchase that I am trying to submit for review. One of the requirements is a screenshot. I have tried uploading multiple screenshots of multiple sizes, all drawn from the documentation, but every one of them is rejected as the wrong size. The screenshots are coming straight out of the simulator, and I have verified that the dimensions match those in the documentation. What else can I do to move this along so I can submit my in-app purchase and my app?

I'm encountering an issue with front camera video recordings via browser (Safari/Chrome) on devices running iOS/iPadOS 18 and above: On iPad, the recorded video appears upside down. On iPhone, the recorded video is rotated 90 degrees. The rear camera functions correctly without orientation issues. This problem seems specific to browser-based recordings, as the native Camera app records videos with the correct orientation. Has anyone else experienced this behavior? Is there a known workaround or fix? The preview while recording is fine, the recorded video is oriented incorrectly.

Hi @AppleSupport, our Apple Developer enrollment for L.T.O consultants Ltd has been stuck in "Processing / Pending" for over 4 months with no response. Our app is ready for launch and we urgently need this escalated. Enrollment ID: 83283WMKJC. Could someone please look into this? Thank you.

Hi Apple, I’m exploring the built-in MCP support in Xcode 27 and noticed that the available Xcode MCP tools don’t seem to provide a way for an agent to manage Swift Package dependencies. For example, an agent can inspect and modify source code, build the project, run tests, and diagnose build issues. However, I haven’t found an MCP tool that allows the agent to perform operations such as: Add a Swift Package dependency to an Xcode project Remove a Swift Package dependency Add/remove a package product from a target Change the version/branch/revision requirement of a package dependency For example, I’d like to be able to give an agent an instruction such as: Add https://github.com/xxx/SomePackage.git to the project, use version 1.2.0 or later, and link the SomePackage product to the MyApp target. At the moment, it appears that the agent can identify that the package is missing when compilation fails, but it cannot actually perform the package configuration step through the Xcode MCP tools. Is Swift Package dependency management intentionally not exposed through Xcode MCP at this time? If it is not currently supported, are there plans to expose APIs/tools for managing: Package dependencies Package products Target-package relationships Package version requirements This would be particularly useful for coding agents, since adding a dependency is a common part of an otherwise automated development workflow. I've submitted a request to feedback, the id is FB24676163. Thanks!

I've tried to add the "Pass Type Identifiers" entitlement manually in .entitlements, but it will not archive and shows the error: Entitlement com.apple.developer.pass-type-identifiers not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. It works correctly for the App (parent of ), but without it the App Clip can't see any passes. The documentation says this should be possible: Note In iOS 17 and later, App Clips can use the Wallet capability. For more information on functionality that’s available to App Clips, see Choosing the right functionality for your App Clip. It is not visible in the portal either. Is this an entitlement that I need to specifically request, and if so, how would I go about doing so? Thanks! Wes

Hi everyone, We submitted our enrollment application for the App Store Small Business Program on August 9, 2026 (almost 1 month ago) and received the confirmation email, but have not had any status update since. Our Agreements, Tax, and Banking page in App Store Connect has been fully set up and Active since February 2026 (Paid Apps Agreement, Bank Account, W-8BEN, DSA Compliance all active). We are well under the $1M threshold with no associated accounts. We have open cases with Developer Support (Case #20000152216769) and Finance Support (Case #22032895, Team ID: N2WHU2B9BC). Could an Apple staff member or moderator kindly help escalate this to the Agreements & Contracts review team? Thank you!

How to get a refund for one of the payments ? Of course the apple invoice from the apple developer program sends me to apple consumer support. They then send me back to the apple developer program.

First time app submission. Business account. Platform: iOS Category: Sports Nothing controversial. No wagering. No adult content. No health-related topics or information. Free app. No in-app purchases. Originally submitted August 8. Included all the standard information. Provided a video walk-through. First review August 14 (six days later). Rejected literally in the same minute the review was opened. Reviewer (?bot) requested additional information. 99% of the information the reviewer requested had already been provided in the original submission. We immediately provided the requested information. August 17 the second review came through. The app was rejected due to "4.3(a) - Design - Spam. - Submitting an app with the same source code or assets as other apps already submitted to the App Store. Creating and submitting multiple similar apps using a repackaged app template. Purchasing an app template with problematic code from a third party. Submitting several similar apps across multiple accounts". The reviewer suggested we "submit a unique app with distinct content and functionality". This made absolutely no sense. We coded the app completely in-house. No third party. No templates. This is the only app we have submitted. We don't have any other accounts. There are literally no other apps that do what ours does. We have two pending patents on the technology. We developed four of our own computer vision models trained on literally thousands of images. The app is completely unique. We provided a detailed response on the same day (August 17), explaining all of the above and attaching our two patent documents. We've worked 9 months on developing this technology and application. The suggestion to just create a new "unique app" seems trite. Four days later, still zero response. It almost feels like nobody is actually reviewing the app at all. At best, they are taking a cursory one-minute look and just hitting reject and moving on to the next developer's submission. Any ideas or suggestions, other than starting a new business and inventing another new technology so we can create a different app as Apple suggests?

when i try to enroll my account to developer to download app in it i receive this mas ( Your enrollment could not be completed) (Your enrollment in the Apple Developer Program could not be completed at this time.)