Search results for

İOS 26 beta battery %1

250,760 results found

Post

Replies

Boosts

Views

Activity

Reply to Swift Playground - Types Lesson
For context, I’m using Swift Playground 4.6.4 on macOS 15.6.1. It has two lessons: Learn to Code 1 Learn to Code 2 Your reference to the Types lesson indicates you’re doing Learn to Code 2. Types > Introduction > page 8 introduces the concept of portal, indicating that they’re part of the puzzle world. That concept was introduced in Learn to Code 1 > Commands > Portal Practice. Likewise the concept of switch is in Learn to Code 1 > Commands > Toggling a Switch. [quote='800744021, Adiv_Abramson, /thread/800744, /profile/Adiv_Abramson'] I cannot write code to call methods or set properties on objects about which I have no useful information. [/quote] If you’re asking questions like this then I suspect that Learn to Code isn’t really for you. You might be better off starting with The Swift Programming Language, using a general playground, or a playground in Xcode, to play with the many examples it contains. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical S
1d
Reply to Wifi Aware iOS devices authentication fails after a period of time
If you can reproduce the problem with our sample code then the path forward here is clear: File a bug against Wi-Fi Aware explaining how to reproduce the issue with our sample. When you file a bug you’ll be asked to include a sysdiagnose log. Trigger that log immediately after seeing the problem. And our Bug Reporting > Profiles and Logs page has a Wi-Fi for iOS/iPadOS entry that explains how to enable additional Wi-Fi specific logging. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to Unabe to use writeHEIFRepresentation - failed to add image to the PhotoCompressionSession.
@DTS Engineer Thanks for the info on the logging. Here is the error: -[CIContext(ImageRepresentation) _CMPhotoRepresentationOfImage:depth:allowAlpha:containerFormat:colorSpace:options:error:] failed to add image to the PhotoCompressionSession. (kCMPhotoError_InvalidData) I also caught the error and printed it out in Xcode: Error Domain=CINonLocalizedDescriptionKey Code=3 (null) UserInfo={CINonLocalizedDescriptionKey=failed to write HEIC data to file., NSUnderlyingError=0x15b1295f0 {Error Domain=CINonLocalizedDescriptionKey Code=10 (null) UserInfo={CINonLocalizedDescriptionKey=failed to add image to the PhotoCompressionSession.}}} This code works on iOS 18. Also, as stated above, I'm able to write the JPG and PNG versions of this image. I was able to get a heif image created by using a CGImage and doing: CGImageDestinationCreateWithURL CGImageDestinationAddImage CGImageDestinationFinalize Hope this helps.
1d
Unabe to use writeHEIFRepresentation - failed to add image to the PhotoCompressionSession.
I'm getting an error writing a ciImage as a heif image: // Create CIImage directly from pixel buffer let ciImage = CIImage(cvPixelBuffer: pixelBuffer, options: [CIImageOption.properties: combinedMetadata]) // Write HEIC synchronously do { try ciContext.writeHEIFRepresentation(of: ciImage, to: url, format: .RGBA8, colorSpace: colorSpace) The error I'm getting is: Error Domain=CINonLocalizedDescriptionKey Code=3 (null) UserInfo={CINonLocalizedDescriptionKey=failed to write HEIC data to file., NSUnderlyingError=0x11b1a1ec0 {Error Domain=CINonLocalizedDescriptionKey Code=10 (null) UserInfo={CINonLocalizedDescriptionKey=failed to add image to the PhotoCompressionSession.}}} Both try ciContext.writeJPEGRepresentation(of: copiedCIImage, to: url, colorSpace: colorSpace, options: options) and try ciContext.writePNGRepresentation(of: copiedCIImage, to: url, format: .RGBA8, colorSpace: colorSpace) work. I also verified that the code works with iOS 18. Is there something new we need to do for Heif images? Thanks
2
0
138
1d
Reply to iOS Build Memory Access Issues Causing Crashes
This has all the hallmarks a subtle memory management bug, possibly one that triggered by threading issues. These often result in weird behaviour like this. It looks like you’ve already tried ASan and TSan, which is a good. The other most popular tool for such issue is zombies. You should try that. See Standard Memory Debugging Tools for info and documentation references. One thing to note here is that ASan and TSan only work with code that you build. If the problem lies in a third-party library that you get as a binary rather than source code, these tools won’t help. And so… [quote='800689021, reidly, /thread/800689, /profile/reidly'] Removing all 3rd party libraries or frameworks … mostly worked in that the crashes went away [/quote] Did you try doing this incrementally? If you have a bunch of them, it’d be interesting to see which combinations do and don’t reproduce the problem. Finally, please post some example crash reports. I don’t need dozens, but a few that illustrate the more common
1d
Reply to iOS26中ALAssetsLibrary 编译报错问题
Sadly, I can’t read Chinese, so I’m answering based on a machine translation. I tried this out here in my office and saw exactly the same problem: Using Xcode 26.0, I created a new project from the iOS > App template. In one of the Swift files, I added the line import AssetsLibrary. The compiler errors with Failed to build module 'AssetsLibrary'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 6.2 effective-5.10 (swiftlang-6.2.0.17.14 clang-1700.3.17.1)', while this compiler is 'Apple Swift version 6.2 effective-5.10 (swiftlang-6.2.0.19.9 clang-1700.3.19.1)'). Please select a toolchain which matches the SDK. This is obviously a bug and I encourage you to file a report about it. Please post your bug number, just for the record. Having said that, Assets Library was deprecated in iOS 9 and Xcode 26’s minimum supported deployment target, per the table on this page, is iOS 15. There is literally no way to use Xcode 26 to
Topic: Media Technologies SubTopic: General Tags:
1d
iOS26中ALAssetsLibrary 编译报错问题
mac os 系统版本:26.0 (25A354) Xcode版本:Version 26.0 (17A324) 项目编译报错 `SwiftExplicitDependencyCompileModuleFromInterface arm64 /Users/zhz/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/AssetsLibrary-HTIJ05N58KN3.swiftmodule /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS26.0.sdk/usr/lib/swift/AssetsLibrary.swiftmodule/arm64e-apple-ios.swiftinterface:10:25: error: 'ALAssetsLibrary' is unavailable in iOS: Use PHPhotoLibrary from the Photos framework instead 8 | public import _StringProcessing 9 | public import _SwiftConcurrencyShims 10 | extension AssetsLibrary.ALAssetsLibrary { | `- error: 'ALAssetsLibrary' is unavailable in iOS: Use PHPhotoLibrary from the Photos framework instead 11 | #if compiler(>=5.3) && $NonescapableTypes 12 | @available(iOS, introduced: 9.0, deprecated: 9.0, obsoleted: 26.0) /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS26.0.sdk/System/Library/Frameworks
2
0
276
1d
ISP DNS Resolution in Full-Tunnel VPN
I am running a full-tunnel VPN using a Packet Tunnel Provider. During VPN setup, we configure DNS setting with specific DNS servers for all domains to be used by the tunnel. However, our project requires DNS resolution for every domain from both the VPN-provided DNS servers and the ISP’s DNS servers. When I attempt to use c-ares or other third-party libraries to resolve domains via the ISP DNS servers, these libraries only detect and use the VPN DNS servers instead. As a result, all queries fail. Is there a way on iOS to programmatically determine the ISP DNS servers while a full-tunnel VPN is active, or a system API that allows DNS queries to be explicitly resolved using the ISP’s DNS servers?
1
0
54
1d
Reply to ISP DNS Resolution in Full-Tunnel VPN
[quote='800664021, mayank_nag, /thread/800664, /profile/mayank_nag'] our project requires DNS resolution for every domain from both the VPN-provided DNS servers and the ISP’s DNS servers [/quote] Why is that? For context, most folks who hit problems like this are trying to use a packet tunnel tunnel provider for something that’s not VPN, something we specifically we don’t support. TN3120 Expected use cases for Network Extension packet tunnel providers talks more about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to Unabe to use writeHEIFRepresentation - failed to add image to the PhotoCompressionSession.
When you get this error, do you see anything relevant in the system log? Specifically, look for log messages with a subsystem of com.apple.coreimage and a category of api. See Your Friend the System Log for lots of hints and tips for wrangling the system log. In this case, however, the process is pretty simple: Launch Console. Make sure Action > Include {Info,Debug} Messages are checked. Select your iOS device on the left. Paste subsystem:com.apple.coreimage into the search box. And, after that, past category:api. Click “Start streaming”. And then reproduce the issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to iOS 26: "TLS failed with error: -9808"
Is this server available on the public Internet? If so, can you share the host name? Oh, and just to be clear: [quote='858269022, mitsubish, /thread/800607?answerId=858269022#858269022, /profile/mitsubish'] The chain is leaf + intermediate only, while it's supposed to be leaf + intermediate + root. [/quote] That is, as I’ve come to expect from LLMs, nonsense. The TLS specs are very clear that the server is not required to include the root. Specifically, RFC 8446 says: Because certificate validation requires that trust anchors be distributed independently, a certificate that specifies a trust anchor MAY be omitted from the chain, provided that supported peers are known to possess any omitted certificates. Earlier TLS RFCs had similar wording. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to How to configure macOS app permission MANUALLY (not GUI)
I’m not sure I understand the question here. You wrote: [quote='800774021, manfred_k, /thread/800774, /profile/manfred_k'] Security Settings -> Network [/quote] That’s not a thing. Are you referring to System Settings > Privacy & Security > Local Network? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to App signing fails after account upgrade
There was a glitch in the provisioning profile matrix at the start of the week, and I think you might’ve managed to hit the relatively small window when it was causing problems. On this thread I have some info on how you can check that, and others have posted various ways to clear the cached info that’s causing the problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d