Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design,hoping for the best. Thanks.

Hello, I’ve enrolled in the Apple Developer Program for over 3 days now, and my enrollment is still pending. I have tried Apple Developer Program Support but, no response. How long does it usually take for my enrollment to be accepte? Especially for someone outside of the US. Thanks.

Hi everyone, We're facing an issue with Universal Links on iOS 18 and above. The problem seems related to how iOS handles redirects before reaching a Universal Link. ✅ Working Link (direct): When we open this direct Universal Link, the app opens as expected: 👉 https://dl.punchh.com/deeplinks/logansroadhouse/ ❌ Not Working (redirected link): This marketing/tracking link eventually redirects to the above Universal Link, but on iOS 18+, it opens the App Store or a browser instead of the app: 👉 https://ip2.loyalty.logansroadhouse.com/ls/click?upn=... The same redirect link works fine on iOS 17 and below — it opens the app.

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?

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.

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

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, 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.

«Hello everyone, after installing iOS 26, I noticed that on my iPhone 13 Pro, which had its battery replaced, the battery status in the settings shows 0%, and the phone does not charge more than 1%, no matter how long I leave it plugged in. The same problem is observed on iPhones 14 and lower where the battery (FB18154101) was replaced.»

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

With ios 26 the chapter images are not updating anymore. At first I thought this is carlay related but it also occures when the phone is connected only through USB or bluetooth to play a podcast. I tried Apple podcasts and other apps like Pocketcast or audible. Same problem. The phone shows the correct chapter image while my car shows the inital image all the time. Even tried a different car :-) I checked focus and settings but found nothing related. With ios18 everything works fine. Any ideas?

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

Environment: macOS 26.3 (25D125) Terminal.app 2.15 (466) Apple Silicon Input method: Japanese (Romaji) - built-in Kotoeri Issue: Terminal.app crashes consistently when typing Japanese text using the built-in Japanese input method (Romaji) and the input line wraps beyond the terminal width. Steps to Reproduce: Open Terminal.app with default profile (Basic) Set terminal window width to ~80 columns Start typing Japanese text using macOS built-in Japanese input (Romaji) Continue typing until the text wraps to the next line Wait a few seconds after the wrap occurs Terminal.app crashes Key info from crash report: Crash thread name: (input method 992 com.apple.inputmethod.Kotoeri.RomajiTyping) ASI: BUG IN CLIENT OF LIBMALLOC: memory corruption of free block Exception: EXC_BREAKPOINT (SIGTRAP) Stack trace involves: IMKInputSession_Modern setMarkedText → SendTextInputEvent → NSTextInputContext The crash occurs in _xzm_xzone_malloc_freelist_outlined called from _CFRuntimeCreateInstance → __CFStringCreateImmutableFunnel3 → +[NSString stringWithUTF8String:] Notes: Does NOT occur with paste input, only with live IME typing Does NOT occur with ASCII-only input Reproducible multiple times per week with normal Japanese usage iTerm2 does not exhibit this issue The crash appears to be a use-after-free or buffer miscalculation in Terminal.app's handling of marked text (未確定文字列) during line wrapping Has anyone else experienced this? Any known workarounds other than switching to iTerm2?

When I try to create a post in Apple Support Community, it forces me to create a new account (for some supersmart reason because my apple account is apparently not enough). In this process, I am required to pick a new username and choose my communications preferences. The next screen? 403 Forbidden Error page.

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.

Hello, Can anyone tell me what this means? Or if it's normal? I'm seeing about 10% battery drain per day on sleep, and pmset -g log shows wakes nearly every minute. 2025-06-10 17:10:35 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 5 secs 2025-06-10 17:10:43 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:13:49 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 8 secs 2025-06-10 17:14:01 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:14:10 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:15:01 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:16:31 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:18:07 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs Looking at one section of them: 2025-06-10 22:00:46 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:90%) 6 secs 2025-06-10 22:00:46 -0700 WakeDetails DriverReason:smc.70070000 - DriverDetails: DriverReason:wifibt - DriverDetails: DriverReason:SMC.OutboxNotEmpty - DriverDetails: 2025-06-10 22:00:46 -0700 HibernateStats hibmode=3 standbydelaylow=0 standbydelayhigh=0 35177 2025-06-10 22:00:46 -0700 WakeTime WakeTime: 0.094 sec 2025-06-10 22:00:46 -0700 Kernel Client Acks Delays to Sleep notifications: [Port-USB-C driver is slow(msg: SetState to 0)(60 ms)] 2025-06-10 22:00:46 -0700 Kernel Client Acks Delays to Wake notifications: [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(121 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(59 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(120 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(123 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(116 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [powerd is slow(5915 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(64 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(119 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(122 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(117 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(76 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(76 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(119 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: DidChangeState to 1)(76 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(121 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(58 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(117 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(76 ms)] 2025-06-10 22:00:48 -0700 com.apple.sleepservices.sessionTerminated SleepService: window has terminated. 2025-06-10 22:00:52 -0700 Assertions PID 323(powerd) Released InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:05 id:0x0xd00009032 [System: PrevIdle] 2025-06-10 22:00:52 -0700 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:90%) 14 secs 2025-06-10 22:00:53 -0700 Assertions Summary- [System: PrevIdle] Using Batt(Charge: 90) 2025-06-10 22:00:53 -0700 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=6474 wakeAt=2025-06-10 23:48:48 info="DHCP lease renewal"] [*process=dasd request=SleepService deltaSecs=979 wakeAt=2025-06-10 22:17:13 info="com.apple.dasd:501:com.apple.intelligenceplatform.IntelligencePlatformCore.Pipeline.FastPass"] [process=powerd request=TCPKATurnOff deltaSecs=227969 wakeAt=2025-06-13 13:20:22] [process=powerd request=CSPNEvaluation deltaSecs=2005 wakeAt=2025-06-10 22:34:18] [process=powerd request=UserWake deltaSecs=7086 wakeAt=2025-06-10 23:59:00 info="com.apple.alarm.user-visible-com.apple.donotdisturb.server.ScheduleLifetimeMonitor.timer,619"]

I’m looking for iOS and Apple Watch users to help beta test ChoreFit, a fitness app that transforms everyday chores into measurable workouts using NEAT (Non-Exercise Activity Thermogenesis) science. What it does: • Tracks chores like vacuuming, mopping, and laundry as real workouts • Syncs with Apple Health for steps, heart rate, and calories • Lets you start or pause chores right from your Apple Watch • Adjusts effort based on body weight and optional weighted vests What I need from testers: • Install via TestFlight (link provided once approved) • Use the app during normal household tasks • Share feedback on usability, Apple Watch sync, and calorie accuracy If you’re interested in movement tracking, fitness analytics, or wearable integration, I’d love your help validating and refining this app before public release.

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)