Search results for

İOS 26 beta battery %1

253,687 results found

Post

Replies

Boosts

Views

Activity

PHPhotoLibrary.performChanges completionHandler not called when deleting assets on iOS 26
In my app, I use api provided in Photos framework to delete specified photo. But after upgrading to iOS 26, the delete function in some iOS device no longer work. The api will never triggers the system confirmation dialog, and the completionHandler is never called. In the iOS Photos app, deletion works correctly on the same assets, but calling the API from my app does not work. Steps to Reproduce Make sure the app has Full Photo Library Access. Execute the following code: PHPhotoLibrary.shared().performChanges({ let assetsToBeDeleted = PHAsset.fetchAssets(withLocalIdentifiers: delUrls, options: nil) PHAssetChangeRequest.deleteAssets(assetsToBeDeleted) }, completionHandler: completionHandler) Expected Behavior The system should present a confirmation dialog asking the user to delete the selected photos. After the user confirms, the deletion should occur, and the completionHandler should be called with success or error. Actual Behavior The system delete confirmation dialog do
2
0
157
5h
Reply to PHPhotoLibrary.performChanges completionHandler not called when deleting assets on iOS 26
Thanks for the follow-up. The issue is currently observed on my user devices (only 3 users not all users are affected). Since I don’t have direct access to these devices, it’s difficult to install and test with a sample app. However, based on the app logs, I can confirm that the API was executed but the completionHandler was never called. I’ve also noticed similar reports from other apps related to iOS 26, for example: https://support.google.com/photos/thread/380562887/cannot-delete-photos-directly-from-device-ios26?hl=en For delUrls, the name might be a bit misleading, but it’s simply an array of PHAsset.localIdentifiers, and the format appears normal in the logs. Even if the localIdentifiers were invalid, I expect that the completionHandler should still be invoked with an error rather than never being called at all.
5h
how to handle setup for NFC without NDEF & PACE and still support iOS 15.0
We have NFC capabilties enabled for our app ID - com.uob.mightyvn but our minimum deployment target is 15.0. We do not have an option deselect PACE from provisioning profile. Hence, the validation is failed for IPA. Invalid entitlement for core nfc framework. The sdk version '18.2' and min OS version '15.0' are not compatible for the entitlement 'com.apple.developer.nfc.readersession.formats' because 'NDEF is disallowed'
2
0
286
5h
Reply to Sheet background in share extension ignores Liquid Glass effect in iOS 26/Xcode 26
Ok, now I have reported this issue via Feedback Assistant under the ID FB20934974 (Sheet background in share extension ignores Liquid Glass effect in iOS 26/Xcode 26). If you require any additional information, sample code, or detailed repro steps, please let me know. I am happy to provide further details to assist with investigation. Thank you for your support and looking forward to updates regarding the Liquid Glass effect in share extension sheets on iOS 26. Best regards,
Topic: UI Frameworks SubTopic: General Tags:
5h
Crash occurring when authenticating user for Game Center
I am using the latest version of the Game Center plugin for Unity and have noticed that my game will crash on launch when trying to authenticate. I've tried this in an empty project with just the plugin and it still crashes with this exception. GfxDevice: creating device client; threaded=1; jobified=0 Initializing Metal device caps: Apple A14 GPU Initialize engine version: 2022.3.62f2 (7670c08855a9) GameKitException: Code=-7 Domain=GKErrorDomain Description=The operation couldn’t be completed. (GKErrorDomain error -7.) (UnsupportedOperationForOSVersion) at Apple.GameKit.DefaultNSErrorHandler.ThrowNSError (System.IntPtr nsErrorPtr) [0x00000] in <00000000000000000000000000000000>:0 Rethrow as TypeInitializationException: The type initializer for 'Apple.GameKit.GKGameActivity' threw an exception. And the area in the native code that is triggering the crash is this inside the GKLocalPlayer_SetAuthenticateHandler function `_onAuthenticate!(tid, _mostRecentAuthenticatePlayer!.passRetainedUnsafeMutabl
1
0
111
5h
PDF Page Content Swapping on iOS 26
Dear Apple Developer Team, On iOS 26, the contents of PDF pages appear to be swapped. Could you please advise if there is a workaround or a planned fix for this issue? Steps to Reproduce: Download the attached PDF on iOS 26. Open the PDF in the Files app. Tap the PDF to view it in Quick Look. Navigate to page 5. Expected Result: The page number displayed at the bottom should be 5. Actual Result: The page number displayed at the bottom is 4. Issue: This is not limited to page 5—multiple page contents appear to be swapped. I have also submitted feedback via Feedback Assistant (FB20743531) on October 20. Best regards, Yoshihito Suezawa
1
0
21
5h
Reply to SwiftUI Instrumentation Fails to start
Hi there! Thanks for the feedback. This must be something else going wrong – we should disallow the recording on iOS devices lower than 26.0, so you should not even be allowed to hit the Record button. Would it be possible to file a feedback with Apple (feedback assistant.apple.com), include screenshot of what you're seeing and sysdiagnose from a target device? Also, please let us know if after recording on the device the new Instrument wouldn't work for some reason. Thanks!
16h
Reply to Potential iOS26 regression on AASA file not download on app install
@DTS Engineer I've submitted a bug report with ID FB20925084. Unfortunately I wasn't able to provide too many details. I'm not able to reproduce this issue on iOS 26 but it was reported by one of my beta testers and the app review team. The issue is now blocking submission of my app to the app store. I'm surprised there are not more reports of this issue. I'd had thought it would affect many apps that use web services or OAuth to authenticate.
Topic: App & System Services SubTopic: General Tags:
16h
Potential iOS26 regression on AASA file not download on app install
Original discussion pre iOS 26 Our app uses Auth0 with HTTPS callback, we've found the issue where AASA file is not ready immediately when app is initially launched, which is the exact issue from the above link. The issue seems mostly fixed on later versions on iOS 18, however, we are seeing some indications of a regression on iOS 26. Here's some measurement over the last week. | Platform | iOS 18 | iOS 26 | |---------------|----------|--------| | Adoption rate | 55% | 45% | | Issue seen | 1 | 5 | | Recover? | Yes | No | This only 1 iOS 18 instance was able to recover after 1 second after the first try, however, all iOS 26 instances were not able to recover in couple tens of seconds and less than 1 minute, the user eventually gave up. Is there a way to force app to update AASA file? Are there some iOS setting (like using a VPN) that could potentially downgrade the AAS
6
0
145
16h
Reply to UVC Capture stops when open Immersive Space
Hi @Lu Linxuan I was unable to reproduce this behavior. Here's what I tried. Download the sample app, Displaying video from connected devices. Remove the entitlements. As of visionOS 26 they are unnecessary. Add a button that opens an immersive space to ContentView. Run the sample and click the button to open the immersive space. The above worked for me. Are you doing something different?
Topic: Spatial Computing SubTopic: General Tags:
18h
Seeking clarification on macOS URLs with security scope
I just saw another post regarding bookmarks on iOS where an Apple engineer made the following statement: [quote='855165022, DTS Engineer, /thread/797469?answerId=855165022#855165022'] macOS is better at enforcing the right behavior, so code that works there will generally work on iOS. [/quote] So I went back to my macOS code to double-check. Sure enough, the following statement: let bookmark = try url.bookmarkData(options: .withSecurityScope) fails 100% of the time. I had seen earlier statements from other DTS Engineers recommending that any use of a URL be bracketed by start/stopAccessingSecurityScopedResource. And that makes a lot of sense. If start returns true, then call stop. But if start returns false, then it isn't needed, so don't call stop. No harm, no foul. But what's confusing is this other, directly-related API where a security-scoped bookmark cannot be created under any circumstances because of the URL itself, some specific way the URL was initially created, and/or manipulated?
15
0
263
18h