https://developer.apple.com/documentation/appstoreservernotifications/app-store-server-notifications-changelog#June-10-2024 ONE_TIME_CHARGE notify type running in a sandbox environment for almost a year, the feature is not yet available for production environment. The notification is already available in Google subscriptions. Our services often miss orders because of the absence of this notification. Can you give us an approximate time range?

I noticed the water lock feature isn’t in the control center after updating to WatchOS 26

I've been trying to add my bank info to my account on AppStore connect, but nothing seems to work. Even searching for my bank does not work for me. Even tried searching for any other bank does not work. Keeps giving error messages. Anyone else experiencing this issue?

Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (smaller than expected with the autofill panel). What I expect / questions: That UIKeyboardFrameEndUserInfoKey (or the related notification) correctly reports the total area covered by the keyboard, including any password autofill panel, when secureTextEntry is active. That the new behavior in iOS 26 be documented if this omission is intentional, or otherwise considered a bug if it is not. If there is any official workaround suggested by Apple for developers affected by this issue while a fix is provided. Thank you for your support.

I set iOS 26 to install overnight, put my iPhone 16 Pro on the MagSafe charger, watched it charge just fine, and went to sleep. When I woke up the iPhone showed the “plug into power” dead battery screen. I took it off MagSafe and put it back on. A half hour later the phone was warm but still wouldn’t power on, just showed the battery screen with a little red in it. I took it off MagSafe and plugged it into my iPad charging brick with USB cable to give it more power, still it did not turn on. I tried holding all the buttons to try to force a restart but didn’t work. For anyone else encountering this, do this to enter DFU mode and restore it. I had to do it a few times before I got the timing right. Plug into your Mac and open Finder (or apparently a PC with Apple Devices or iTunes) Press and quickly release volume up Press and quickly release volume down Press and hold right side button When the battery disappears and screen goes black, hold volume down and continue holding side button After a couple seconds release the side button and continue holding volume down A prompt to allow connecting to the iPhone should appear after a couple seconds, click Allow, and it’ll say the iPhone entered DFU mode - proceed to restore the firmware

Hello everyone! I'm a newly graduated Computer Engineer living in Türkiye. I've been developing my skills in the iOS field for a while now. But sometimes I get lost and don't know what to do. I've just joined this community and have a request for you. I'd be very grateful if you could share your own advice, experiences you've had along the way, and how you successfully overcame them. I'm open to all kinds of positive or negative feedback. Self-improvement is paramount to me.

.fullScreenCover(isPresented: $isShow) { Button(action : { isPresented.toggle() }){ Text("Choose") } .familyActivityPicker( isPresented: $isPresented, selection: $selection) .onChange(of: selection){ value in } } In the official version of iOS 18, when I click the Done button of familyActivityPicker, the fullScreenCover pop-up box will disappear.

I've paid - and have the confirmation of subscription email. But when I try to enroll both on my iphone and macbook air - I get errors. on the iphone said could not complete enrollment. on the macbook it said "not available in your area" I am in australia and it should work. Does anyone know how to fix the enrollment bugs?

I'm trying to understand how UIDevice.current.identifierForVendor behaves when an iOS app is restored via iCloud onto a different physical device. Context I'm building an app that needs to detect whether it’s running on a newly restored device (for example, after the user transfers their iPhone via iCloud setup). To do this, I save the value of UIDevice.current.identifierForVendor?.uuidString in persistent storage (e.g., UserDefaults). The question If I install my app on Device A, store the identifierForVendor value, back up the device to iCloud, and then restore that backup onto Device B, will the restored app see the same identifierForVendor value, or a new one? More specifically: Does iCloud backup/restore preserve the underlying “vendor” ID across devices? Is the identifierForVendor tied only to the bundle identifier and vendor prefix, or also to the physical device hardware? If the user deletes all apps from the same vendor, then restores them from iCloud, is the ID reset? What I’ve found so far Apple’s docs say: “The value of this property is the same for apps that come from the same vendor running on the same device. If the user deletes all of that vendor’s apps from the device and then reinstalls one or more of them, the value may change.” However, it doesn’t explicitly mention what happens after iCloud restore onto a new device. Goal I want to know if it’s safe to use identifierForVendor to detect a new device context (e.g., trigger a refresh of a Firebase token when the user’s device changes). Environment iOS 17+ (latest) Swift / Capacitor app bridge Testing between iPhone 14 Pro → iPhone 15 Pro (iCloud restore)

アプリ開発を依頼して公開中ですが、 アプリ開発会社が倒産し、連絡もつかず、 アップル社への年間料金の支払いができません。 登録アカウントがわかりませんので、どうしたらいいでしょうか？ よろしくお願いいたします。

Hello. I need to develop for iOS 18. I've recently updated Xcode and it says I have to download ios 26 platform. I don't need it, but I can no longer build my existing projects against ios 18, even though Xcode says it's still installed and used 13 days ago. How to I remedy this?

Hello everyone, on August 31st, all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps are in compliance with Apple's policies. I then uploaded a new version and sent it to the review team, but I received the following error "There was an error processing your request. Please try again later." I have contacted Apple via Email and Phone but no one cares about my problem. Has anyone had the same situation as me, I am really worried.

I’m experiencing an issue on macOS Tahoe (Developer Beta, July 2025) related to the new “Allow in Menu Bar” section in System Settings. After uninstalling the application Backdrop (developer: Cindori), the entry com.cindori.Backdrop.Wallpaper still appears in the list of apps allowed to show in the menu bar, even though: — The app and all its associated files have been fully deleted. — The LaunchAgents files in ~/Library/LaunchAgents and /Library/LaunchAgents have been removed. — Preferences have been deleted via defaults delete com.cindori.Backdrop and defaults delete com.cindori.Backdrop.Wallpaper. — The system has been restarted. It seems the “Allow in Menu Bar” section keeps phantom references to apps or agents even after complete cleanup. Could you please confirm if this is expected behavior (perhaps for future reactivation) or a bug? Is there any official method or recommended command to permanently remove such residual entries from this list? Thank you very much for your help and clarifications.

since updating from 18.3 to 18.4, both on cellular and WiFi Networks I can’t connect to the internet. Since the phone wont connect to the internet I’m not able to turn off “find my iPhone“ to restore my iPhone to iOS 18.3 this way my iPhone is useless any ideas / thoughts about this?

Dear Apple Developer team, dear Apple Developer community, I’m posting this publicly because I honestly don’t know how else to get a response. Timeline: December 3rd: I applied for the Apple Developer Program and received the confirmation email: “Your program enrollment has been received.” After that: complete silence for weeks – no status updates, no emails, nothing. End of December: Only after I opened a support ticket myself did I receive a response asking me to upload additional documents. January 12th: I uploaded all requested documents in full. Since then: silence again. Last Monday, I sent a follow-up email → no reply. Today (January 26th), I opened a new ticket, referencing the existing case number. Honestly, I have to ask: Where is the professionalism in this process? For comparison: The Google Play Developer account verification (including identity and company checks) took around 24 hours. Apple is one of the most valuable technology companies in the world. Why does a basic developer enrollment take over two months, without transparent communication or even a simple status update? At this point, I would really appreciate: a clear status update, or at least a realistic timeline for when this process will be completed Right now, this experience feels neither professional nor developer-friendly. Thank you for reading, and I sincerely hope for a timely response.

I have developed three apps using the Screen Time API. The following are common problems I encountered in the three apps: DeviceActivityMonitorExtension is automatically killed after running for a few days (frequently) The same DeviceActivityEvent in DeviceActivityMonitorExtension is triggered twice during eventDidReachThreshold (especially obvious in iOS18.5) Screen Time authorization is automatically canceled for no reason (occasionally) I hope to get help

I'm suddenly receiving zero products from SKProductsRequest, even though this setup previously worked without issues. The debugger shows that both of my product identifiers are now being returned under invalidIdentifiers, and response.products is empty. I’ve confirmed the following: There are no pending agreements in App Store Connect. The subscription is active and configured correctly. The product identifiers match exactly with what’s defined in App Store Connect. Here is the delegate method I'm using (unchanged from when it previously worked): extension UpgradeViewModelProvider: SKProductsRequestDelegate { func productsRequest(_ request: SKProductsRequest, didReceive response: SKProductsResponse) { if response.products.count > 0 { delegate.send(.onProduct(response.products)) } } } Since everything was functioning before, I’m trying to understand what may have caused the identifiers to suddenly be marked as invalid. Any guidance or suggestions on what to check next would be greatly appreciated.

After the last OS26 developer beta update the watch series 6 battery drains fast, in less than two hours life. I visited Apple Store , they said the battery was dead so I had to buy new watch series 10 The same issue happened in the new watch, the battery meter shows 50% after 1 hour Right now I’ve downgraded my update version to beta 11 until I can find a solution

Guideline 2.3.1 - Performance The app contains hidden features. Specifically, we still noticed that your app includes code which causes it to behave differently during the review process regarding web game presentation and payment. It would be appropriate to ensure that all features and functions in the app are visible and fully accessible during review. Guideline 3.1.1 - Business - Payments - In-App Purchase The app allows users to purchase digital content natively or via a web view in the app using payment mechanisms other than in-app purchase. Apps cannot include in-app payment mechanisms other than in-app purchase. Apps on the United States storefront may also include buttons, external links, or other calls to action to direct users to payment mechanisms other than in-app purchase. We have been rejected three times due to hidden functions and issues with web payment and web games. However, in the last package we submitted for review, it was confirmed that the code related to web games was removed, and the code related to web interaction JS bridging payment calls was also removed Dear experts, we sincerely invite you to offer your valuable suggestions. If you have any experience of meeting us, please share with us. We would be extremely grateful

Hello, In my App.xcdatamodeld I have an entity called File. When I am building the project with Xcode, file FileEntity+CoreDataProperties.swift is generated. After upgrading Xcode to version 26.0 (17A324), I am getting the warning: Public import of 'CoreData' was not used in public declarations or inlinable code Any idea how to get rid of this warning since it's a generated file and I can't see any option to change it?