Search results for

İOS 26 beta battery %1

253,912 results found

Post

Replies

Boosts

Views

Activity

Reply to Icon Composer and Xcode building time
Hi, I'm seeing the same thing. I want to use AlternateAppIcon, so I added 7 AppIcon-x.icon files to my project in Xcode 26, and these icon files are created by icon composer software. And I also see the AssetCatalogSimulatorAgent(370% CPU). Finally, it took 30mins to build succeeded project. Very slowly. What should I do?
1w
DriverKit IOUserSerial Driver
Hello everyone. After a lot of research and some tests from various sources, I have actually built a small SerialDriverKit IOUserSerial driver. Unfortunately, the documentation on the official sites is tight-lipped and very thin. At least I have a running driver instance. Now my request and question: Can anyone give me a tip on how to get the data from the serial client? I have already called IOUserSerial::ConnectQueues(...) in the IOUserSerial::Start() method and I got the IOMemoryDescriptors for interrupt, RX and TX to my driver instance. I tried to get access to the memory in the method IOUserSerial::TxDataAvailable() with IOMemoryDescriptor::CreateMapping(...). Unfortunately, no data is coming in. It's always 0x00. Here is the OS log: kernel: (org.eof.tools.VSPDriver.dext) kernel: (org.eof.tools.VSPDriver.dext) [VSPDriver] init called. kernel: (org.eof.tools.VSPDriver.dext) [VSPDriverPrivate] constructor called. kernel: (org.eof.tools.VSPDriver.dext) [VSPDriver] start called. kernel: (org.eof.tools.VSPDri
19
0
1.1k
1w
Reply to Core Bluetooth and app background launch
You seem to have misunderstood. That note, Note 5, only pertains to the specific cases where Note 5 is referred to, namely: if the app Force Quit by the user Control Center Bluetooth button toggled An app that was force quit was never able to be relaunched before. iOS 26 actually adds the capability for such apps to be launched if they opt in to use AccessorySetupKit. So, this is not a case of apps losing the capability to relaunch, but a case of apps gaining the capability to relaunch in cases where they weren't able to before, if they use AccessorySetupKit.
Topic: App & System Services SubTopic: Core OS Tags:
1w
Core Bluetooth and app background launch
TN 3115 states that apps that do not use AccessorySetupKit will loose the ability to launch into the background to service bluetooth in iOS26. Starting in iOS 26 and iPadOS 26, only apps that use AccessorySetupKit to setup Bluetooth accessories will be relaunched. Is there any more information regarding this? Will it affect any app under iOS26 or only those build against the iOS26 SDK? My app (dev build) is still relaunched, even though I'm running iOS26, so I wonder if there are any more conditions checked.
1
0
43
1w
Migration Subscription API returns 500 error
We got Advanced Commerce API and the generic product identifiers approved. When I was try to migrate a sandbox subscription to ACA enabled subscription I hit an error Request payload (Hid some info but the requestReferenceId is the real) { descriptors: { description: Migrated, displayName: Migration }, items: [ { sku: product_1mo_999, description: description, displayName: Product } ], requestInfo: { requestReferenceId: 3b0b8e67-d8a0-45f4-8f6d-06bffa9a2c08 }, storefront: USA, targetProductId: com.company.generic.subscription, taxCode: C003-00-1 } Response { errorCode: 5000000, errorMessage: An unknown error occurred. }
4
0
205
1w
VoIP / PushKit notification failure on versions of iOS 18
We are trying to figure out a strange issue. Our app has not changed for at least 10 months but my devices and the QA tester device have all stopped receiving push/call notifications for twilio voip The twilio credential and apple voip services certificate are in date and valid It is pointing to the correct bundle id and topic (not changed configuration for years) token passed in to TwilioVoiceSDK.register() is retrieved from PKPushRegistry as per guide Running locally the Twilio Voice SDK successfully registers and retrieves APNs token What is interesting is if I log in with exactly the same client account on an iOS 18.5 device (and an older iPad) call notifications work perfectly (I have made sure all focus modes/dnd are off and notification settings are identical) The only changes myself and QA have made recently is minor iOS 18 version updates - 18.6.2 and 18.7.1 These now receive Invalid device token from APNs when Twilio attempts to create a call/voip notification for the user identity
1
0
69
1w
Low-Latency HLS stream playback issue on iOS 26
We have a Low-Latency HLS stream, and on iOS 26, even though the bandwidth is sufficient, it still selects a low-bandwidth resolution (e.g., RESOLUTION=640x360) for playback instead of using a higher-bandwidth resolution (e.g., RESOLUTION=1920x1080) when using AVPlayerViewController with AVPlayer. This works fine on iOS version 18 and previous versions. What could be the solution to this issue?
1
0
158
1w
Reply to TCC Permission Inheritance Failure: Swift Parent -> Python Child
Thanks for all the answers. What you’re dealing with here is the responsible code problem. When a process performs a privileged operation, macOS has to track down the responsible code so that it can check whether that code has TCC privileges or not. In general, macOS will follow the chain from child process to parent process to determine process responsibility. However, things are not that simple: The child process might be doing things to break the chain. There are also situations where macOS doesn’t follow the chain as you might expect. I have a test project that I use to exercise cases like this, and it seems to be working for me. Here’s what I did today: On macOS 15.7.1, I went to System Settings > Privacy & Security > Input Monitoring and confirmed that there’s no entry for my test app there. I used Xcode 26.0.1 to build and run the app. I started input monitoring within the app. The system presented the permissions alert. I clicked Open System Settings. And enabled Input Monitoring in System S
1w
Reply to SMAppService
[quote='864383022, spacecash21, /thread/804561?answerId=864383022#864383022, /profile/spacecash21'] it seems like macOS memory protection kicks in and does not allow starting/restarting different executable. [/quote] Hmmm, I’m not sure how memory protection is a factor here. The log snippet you posted suggests that your daemon is crashing. Does that generate a crash report? If so, please post it here. See Posting a Crash Report for advice on how to do that. Also, how are you updating your app? Make sure that you’re not hitting the problem described in Updating Mac Software. Specifically, use the instructions in Check Third-Party Software Updaters to verify that your new daemon was written to a new file with a new inode number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Reply to Wi-Fi Raw Socket Disconnection Issue on iPhone 17 Series
Thanks for the clarifications. Just FYI, in networking, raw socket usually refers to raw IP sockets, hence my confusion. So, lemme summarise the issue: You have an iOS app. It talks to a Wi-Fi based accessory over TCP. With iPhone 16, this all works as expected. With iPhone 17, things go wrong, such that your TCP socket disconnects after 20 seconds. After that, your app is unable to reconnect. And the only way to resolve the issue is to restart the Wi-Fi subsystem on your accessory. Is that right? If so, this sounds eminently bugworthy. While there are lots of ways that local networking can go wrong, the fact that this fails when the only variable you change is moving from iPhone 16 to 17 suggests that it’s caused by a Wi-Fi level issue on iPhone 17. DevForums focuses on Apple APIs and tools, and isn’t really set up to help with Wi-Fi level issues. Given your description of the problem, I think it makes sense for you to file a bug so that our Wi-Fi engineering team can investigate. In your bug, make
22h
Reply to XPC Service Installed Outside App Doesn't Set Responsible
[quote='864274022, TyngJJ, /thread/805696?answerId=864274022#864274022, /profile/TyngJJ'] I'm using the terminology from an older document [/quote] Yeah, the terminology here is confusing, which is why I’ve switch to named XPC endpoint. It’s long and clumsy [1], but it’s very clear. Unfortunately there’s no way to get that older doc fixed, because the Documentation Archive is a read-only snapshot. You can’t use the responsible process constraint on a launchd daemon or agent because its named XPC service is published to a Mach bootstrap namespace that allows multiple clients to connect. The first client starts your process and then subsequent clients trigger a new connection to that same process. Given that, the concept of responsible process doesn’t really make sense [2]. What you’re really trying to do here is to ensure that your agent only does work on behalf of your app, and that’s the problem that XPC peer constraints solve. In the case of an launchd agent, it’s best to apply XPC peer constraints
1w
VNDocumentCameraViewController UI issues in iOS 26
We're observing several UI issues with VNDocumentCameraViewController on devices running iOS 26. These screens were functioning correctly in earlier iOS versions. Issue 1 - On the edge correction screen, the top bar now appears as a gray strip beneath the status bar, whereas in previous iOS versions, it was positioned at the bottom of the screen. Do we have any workarounds to address this issue? Issue2 - The edit buttons and their labels are not clearly visible, affecting usability. Im using XCode 16.4 to build to iOS26 and the usage is like below: `let scanner = VNDocumentCameraViewController() scanner.delegate = self self.present(scanner, animated: true)`
1
0
119
1w
Reply to VNDocumentCameraViewController UI issues in iOS 26
Following up on this issue, specifically - the edge correction screen top bar positioning issue is significantly impacting our app. To provide more context: The grey strip appearing beneath the status bar (instead of at the bottom) makes the UI appear broken to users. The issue is consistent across all iOS 26 devices we've tested. Custom styling or modifications are not possible to the VNDocumentCameraViewController as per my knowledge. Has anyone else encountered this? We'd greatly appreciate: Confirmation whether this is expected behaviour or a known issue. Any recommended workarounds or API changes we should implement Any guidance from Apple Engineering would be highly appreciated.
Topic: UI Frameworks SubTopic: UIKit Tags:
1w