Lately every app that I submit (games) with in app purchases, always coins , the app gets rejected with: Guideline 3.1.1 - Business - Payments - In-App Purchase Your app uses intermediary currency to purchase items that function as non-consumable products but still does not include a restore mechanism. Users restore transactions to maintain access to content that they've already purchased It baffles me that reviewers think buy different number of coins is non-consumable. I have tried to explain that coins will be used to buy weapons and skins and they will also be earned at the end of every level yet for some reasons they are still rejecting the app. It is absurd. This is the second app that I have to go through with this. The first one they eventually figured it out but this one no.
Search results for
İOS 26 beta battery %1
250,828 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
After upgrading to macOS 26, I noticed that showing a Quicklook preview in my app is very slow. Showing small text files is fine, but some other files I've tried, such as a Numbers document, take about 30 seconds (during which the indeterminate loading indicator appears) before the preview is shown. When showing the preview of an app, such as Xcode, the panel opens immediately with a placeholder image for the Xcode icon, and the actual Xcode icon is shown only after about 25 seconds. During this time many logs appear: FPItemsFromURLsWithTimeout timed out (5.000000s) for: file:///.file/id=6571367.2/ (/) FPItemsFromURLsWithTimeout timed out (5.000000s) for: file:///.file/id=6571367.23684/ (/Users) FPItemsFromURLsWithTimeout timed out (5.000000s) for: file:///.file/id=6571367.248032/ (/Users/n{9}k) FPItemsFromURLsWithTimeout timed out (5.000000s) for: file:///.file/id=6571367.248084/ (/Users/n{9}k/Downloads) Failed to add registration dmf.policy.monitor.app with error: Error Domain=NSCocoaErrorDomain Co
I developed an app that uses the Core NFC framework to read tags. The feature works correctly on iOS 18 and earlier versions, but after upgrading to iOS 26, it stopped working. Details: Entitlement Near Field Communication Tag Reader Session Formats D2760000850101 D2760000850101 Info.Plist com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 com.apple.developer.nfc.readersession.felica.systemcodes 12FC Privacy - NFC Scan Usage Description Signing and Capabilities: Near Field Communicating Tag Reading [Eanbled] My Sample Code Is: class NFCManager: NSObject, NFCTagReaderSessionDelegate { private var nfcSession: NFCTagReaderSession? let isConnectionNeeded = false func startNFCSession() { guard NFCTagReaderSession.readingAvailable else { // NFC is not available on this device. return } nfcSession = NFCTagReaderSession(pollingOption: [.iso14443, .iso15693, .iso18092], delegate: self) nfcSession?.begin() } func stopNFCSession() { nfcSession?.invalidate() } // MA
I built the Appvector tool – aso.report, a completely free ASO analysis platform designed to help indie developers easily improve their App Store listings without complex metrics or costly subscriptions. Just paste your app’s URL to get instant insights, multi-country analysis, and actionable recommendations - making ASO simple, accessible, and effective for everyone.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store
App Review
App Store Connect
It was working fine on Xcode 26 RC and with iOS 26 RC devices yesterday. Today I upgraded to Xcode 26 (17A324), then this problem occurred. Deleting all files from ~/Library/Developer/Xcode/UserData/Provisioning Profiles helps.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
[quote='858251022, DTS Engineer, /thread/800521?answerId=858251022#858251022'] I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP. [/quote] I repeated the test described above with Xcode 26 RC and iOS 26.0, and things continue to work. Here’s a summary of my results: Xcode | iOS | Result ----- | --- | ------ 16.4 | iOS 18.6.2 | OK 26.0 RC | iOS 18.6.2 | OK 26.0 RC | iOS 26.0 | OK This is all running on macOS 15.6.1, using a unique bundle ID each time. At this point I’m pretty much convinced that the root cause of this issue is resolved and that the remaining problems are caused by Xcode caching bad state. Unfortunately it’s hard for me to test solutions to that because I’ve never managed to reproduce the problem. [quote='858275022, totofrechou, /thread/800521?answerId=858275022#858275022, /profile/totofrechou'] The answer from Muslim Ismailov in Stack Overflow worked for me [/quote] Cool. That’s very like what I described
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I have had the exact same problem with all projects for the last 12 hours :-/ However I just deleted ALL files and folders from .../Library/Developer/Xcode - which seems to have fixed the problem for me. I'm using MacOS 15.7, Xcode 16.4 and iOS 18.7 on the iPhone I test on. Cheers Thomas
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
My app update submission has been in the Waiting for Review status for over 72 hours. A few days ago I already canceled and resubmitted after 3 days of inactivity, but this time it still hasn’t moved forward. I’d like to check if there might be any issues on my side that I should address, or if this is just part of the current review timelines. The update includes a critical bug fix, and unfortunately I’m losing users while waiting. Is there anything I can do to help move the review process along, or should I simply continue to wait? The problem is getting more absurd, since it is not a new app submission but an update for already existing one. Thank you in advance.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
I recommend not using the default value when including fields. Maybe in iOS 26 the logic behind GestureMask.all changed. Using .subviews helped me.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
The problems are triggered by specific circumstances that I’m not testing. For example, I’m using Xcode 16 and other folks are using Xcode 26. I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP. However, if this issue is what I think it is, Xcode 26 won’t change things. I believe that's the case. In Xcode 26 Automatic signing of all my apps for Ad Hoc distribution appears to be broken. The app archives and exports without errors, but all my devices refuse to install the app, complaining that This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature. I manually created my own provisioning profiles for all the targets, switched from automatic to manual signing and everything works. It's like we're back in 2014 but at least I cut my teeth on all this stuff back in the day so I still remember all the steps required.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I keep getting the following error when trying to run Passkey sign in on macOS. Told not to present authorization sheet: Error Domain=com.apple.AuthenticationServicesCore.AuthorizationError Code=1 (null) ASAuthorizationController credential request failed with error: Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1004 (null) This is the specific error. Application with identifier a is not associated with domain b I have config the apple-app-site-association link and use ?mode=developer Could there be any reason for this?
Topic:
Privacy & Security
SubTopic:
General
Tags:
macOS
Objective-C
Authentication Services
Passkeys in iCloud Keychain
Hi, I have an app that displays tens of short (<1mb) mp4 videos stored in a remote server in a vertical UICollectionView that has horizontally scrollable sections. I'm caching all mp4 files on disk after downloading, and I also have a in-memory cache that holds a limited number (around 30) of players. The players I'm using are simple views that wrap an AVPlayerLayer and its AVPlayerItem, along with a few additional UI components. The scrolling performance was good before iOS 26, but with the release of iOS 26, I noticed that there is significant stuttering during scrolling while creating players with a fileUrl. It happens even if use the same video file cached on disk for each cell for testing. I also started getting this kind of log messages after the players are deinitialized: <<<< PlayerRemoteXPC >>>> signalled err=-12785 at <>:1107 <<<< PlayerRemoteXPC >>>> signalled err=-12785 at <>:1095 <<<< Pl
I have base model M4 mini on Mac OS 26 which keeps removing the docked application launcher. I keep adding it back which works till the next incremental update and it's been removed again. The ONLY way I can stop this from happening is to create an alias to the folder and to add that to the dock. I have 3 devices on the 26 Dev beta and the other 2 do not suffer this issue. I was expecting the release candidate to have resolved this but alas it hasn't.
Topic:
Community
SubTopic:
Apple Developers
Hi, Since iOS 26 introduced the new Games app, I’ve noticed a problem when using a Nintendo Switch Pro Controller in wired USB-C mode, and also with third-party controllers that emulate it (like the GameSir X5 Lite). In the Games app interface, only the L/R buttons respond, but the D-Pad and analog sticks don’t work at all. Once inside actual games, the controller works fine — the issue only affects the Games app UI. What I’ve tested so far: Xbox / PlayStation controllers → work fine in both wired and Bluetooth, including inside the Games app. Switch Pro Controller (Bluetooth) → works fine, including in the Games app. Switch Pro Controller (wired) → same issue as the X5 Lite, D-Pad and sticks don’t work in the Games app. This makes it hard to use the new Games app launcher with these controllers, even though they work perfectly once a game is launched. My question: is this an iOS bug (Apple needs to add proper support for wired Switch Pro controllers in the Games app), or something
Our app server is having some TLS related issue with the new iOS 26 (It works with iOS 18 and below). When opening the domain url in iPhone Safari browser with iOS 26, it showing the error as below: We followed the instructions from this link (https://support.apple.com/en-sg/122756), to run the following command: nscurl --tls-diagnostics https://test.example in Terminal app. It shows TLS failed with error: -9808 Could anyone please help explain what exactly the issue is with our server certificate, and how we should fix it? Thanks so much!