“show when run”

I recently noticed a UX inconsistency while using the battery charge limit feature on my MacBook with a MagSafe charger. With the optimized charging feature, users can set a custom maximum charging limit (for example, 95%) to improve battery health. However, the MagSafe LED indicator continues to show the charging state (amber) even after the device reaches this user-defined limit. Previously, the LED would turn green when charging reached 100%, clearly indicating a “fully charged” state. But now, when charging stops at a user-defined limit, there is no clear visual feedback that charging has effectively completed based on the user’s preference. This creates confusion, as the LED suggests that charging is still ongoing even though the system has stopped charging at the configured limit. A possible approach to improve this could be to treat the user-defined limit as an effective “fully charged” state during charging. For example: if is_charging: if battery_percentage < user_defined_limit: LED = AMB

Hello, Our application has been stuck in the In Review status for 17 days now, and we are looking for guidance on whether this is a known technical stall or an extended policy audit. The Issue: The app moved from Waiting for Review to In Review on March 25th. Since then, there has been no change in status and no messages in the Resolution Center. App ID: 6753868146 Thanks

I've successfully signed Unix apps manually in the past. Today (after signing the new agreement) I can get it to replace the existing signature but it says rejected when I check it. Here are the commands I'm using: michaelleahy@Michaels-Mini ~ % sudo codesign --force --deep --options runtime --sign Developer ID Application: Bookup Corp. (6J8PUT****)” /Users/michaelleahy/Documents/theapp /Users/michaelleahy/Documents/theapp: replacing existing signature michaelleahy@Michaels-Mini ~ % spctl -a -vvvv -t install /Users/michaelleahy/Documents/theapp /Users/michaelleahy/Documents/theapp: rejected source=Unnotarized Developer ID origin=Developer ID Application: Bookup Corp. (6J8PUT****) Here is a command (issued right after the one above) showing an older signed app is accepted: michaelleahy@Michaels-Mini ~ % spctl -a -vvvv -t install /Users/michaelleahy/Documents/olderapp /Users/michaelleahy/Documents/olderapp: accepted source=Notarized Developer ID origin=Developer ID Application: Bookup Corp. (6J8PUT****

I’m looking for a small number of iPhone users to test an app I’ve been building and give honest feedback on the UX. The app is called Triovel. It’s for a problem I kept running into after trips: photos end up in camera roll, plans are buried in chat, and later it’s surprisingly hard to reconstruct what actually happened on each day. The core idea is simple: rebuild or record a trip into a timeline of activities, then attach photos/notes to the right parts of the trip so everything stays together. At this stage, I’m not looking for generic “nice app” feedback. What I need most is feedback on: first-time onboarding clarity whether rebuilding a past trip feels intuitive where the flow feels slow, confusing, or unnecessary whether the timeline structure makes sense right away Good fit if you: recently came back from a trip have an upcoming trip or have old travel photos you never properly organized iPhone only for now. Early beta, so I expect rough edges. If anyone is open to trying it through TestFligh

I am debugging a CloudKit sharing issue in an iOS app that uses NSPersistentCloudKitContainer with Core Data backed sharing. The symptom is that collaboration/share creation appears to succeed locally, but the resulting CKShare never gets a server-backed URL. UICloudSharingController therefore cannot proceed because share.url remains nil. (I do see the UICloudSharingcontroller Dialog and am abble to select people to share, one executed the share icon in the message window just spins After adding extensive logging, it looks like the real problem is not the sharing UI itself, but that Core Data + CloudKit mirroring is already in a bad state before share presentation begins. What I am seeing: Repeated CloudKit import failures with CKError.partialFailure The partial failure always contains one stale share zone with: • CKError.zoneNotFound • server message: Zone does not exist Core Data then repeatedly logs: • NSCloudKitMirroringDelegateWillResetSyncNotificationName • reason: ZoneDeleted • followed by a full mirro

Xcode Cloud builds fail at the export archive step. The critical log shows: Account Session Proxy Provider: Unable to authenticate with App Store Connect Error Domain=DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 (null) And in DVTITunesSoftwareService.log: App Store Connect response failed with unknown failure; response (null); error (null) error: DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy Environment: Xcode Cloud, iOS app, team type Individual (S43L28SVX2) What I have ruled out: Regenerated all DISTRIBUTION_MANAGED certificates (per thread 744683) — portal API is reachable, certs issued successfully Removed an obsolete App Groups entitlement that was causing a secondary error — that error is now gone All agreements accepted, no pending legal items Failure persists across multiple builds with identical symptoms The developer portal API responds correctly. The failure is isolated to the App Store Connect store configuration endpoint specifi

Hi everyone, My new app, was recently approved and its status changed to Ready for Sale in App Store Connect. Everything seems to be working fine technically: I can download the app perfectly using the direct App Store link, and it also appears correctly when I click on my Developer Name. However, when I search for the exact and unique name in the App Store search tab, it doesn't show up at all. I am aware that search indexing can usually take anywhere from 24 to 72 hours, but I wanted to ask if anyone else is experiencing unusual delays with the search index right now? Is there anything else I can do to trigger the indexing process besides waiting or pushing a new update?

Hi everyone, I'm running an Apple MDM service and encountering an issue where a number of devices stop receiving MDM push commands within 10 days of profile installation, even though everything appears to be set up correctly. Environment: MDM profile is installed and verified (status: OK, result: SUCCESS) Devices are cellular-enabled with no connectivity issues APNs certificate is valid (thousands of other devices are communicating normally) The command being sent to devices is DeviceInformationCommand No NotNow response or any check-in received from the affected devices for over a week Issue: We send DeviceInformationCommand to devices to retrieve device information and update the last communication timestamp. However, a subset of devices simply stop responding to this command within 10 days of profile installation. The last communication date is not being updated, and no response — not even a NotNow — is coming back from these devices. Since other devices on the same MDM setup are working fine, I'v

Environment: Xcode Version: Xcode 26.3 Affected iOS Versions: iOS 26.1 and later Working iOS Versions: iOS 26.0 and earlier Tested Devices: iPhone 15 Pro (iOS 26.2) - ❌ Bug presents iPhone 17 (iOS 26.1) - ❌ Bug presents iPhone Air (iOS 26.0) - ✅ Works as expected iPhone 16 Pro Max (iOS 18.0) - ✅ Works as expected Description: We have identified a severe localization regression regarding the setAlternateIconName(_:completionHandler:) API starting from iOS 26.1. Our application is strictly restricted to support only Traditional Chinese (zh-TW / zh-Hant). We have correctly configured CFBundleLocalizations, CFBundleDevelopmentRegion, and explicitly set CFBundleAllowMixedLocalizations to YES in our Info.plist. In iOS 26.0 and earlier, when changing the app icon, the system alert correctly displays in Traditional Chinese. However, in iOS 26.1 and later, the alert unexpectedly falls back to English, completely ignoring the app's localization constraints and the user's preferred device language. Crucial Observation:

Xcode 26.4 on macOS 26.3.1 cannot pair a real Apple Watch for development. iPhone companion is visible and stable in Devices and Simulators. Watch is paired to iPhone and works normally, but Xcode shows: CoreDeviceError Code: 4 RemotePairingError Code: 1007 “The device rejected the connection request.” “Ensure the device is paired with this machine.” What I already tried: trusted Mac on iPhone re-paired Watch with iPhone reconnected iPhone by cable reset authorized computers on Watch restarted devices reopened Devices and Simulators Result: iPhone remains stable Watch is seen intermittently or stays reconnecting / rejects pairing app logic is otherwise working on iPhone side Need: steps to restore Watch ↔ Xcode development pairing without further destructive resets.