Search results for

İOS 26 beta battery %1

250,926 results found

Post

Replies

Boosts

Views

Activity

Reply to Provisioning problem
OK, a quick update… IMPORTANT Please don’t post replies that just say ‘me too’. There’s a Boost button at the top of the thread that you can click in that case. OTOH, if you have new info to share, please post a reply, not a comment. It’s hard for me to keep track of comments. My understanding of this issue is that: It was a problem with the way that the Developer website issued provisioning profiles. It had been resolved at the time I posted that response, about 4:00 Pacific time. Hence my original advice on this thread to run a test with a new, unique bundle ID. I just ran that test myself and I didn’t see a problem. Specifically: Using Xcode 16.4 on macOS 15.6.1, I created a new project from the iOS > App template. In Signing & Capabilities, I confirm that automatic code signing was enabled with my team selected. I selected an iOS 18.6.2 device as the run destination and chose Product > Run. The app ran just fine. However, this is using my extant wildcard provisioning profile, s
3d
Reply to Provisioning problem
[quote='858241022, Siamprodhan, /thread/800521?answerId=858241022#858241022, /profile/Siamprodhan'] 3- Navigate to the Trust section and set it to Always Trust. [/quote] I’m not sure why that helped in your case but this is not a good idea. Modifying certificate trust settings is a common cause of errSecInternalComponent errors. I’m back in the office and I’m gonna take another look at this again once I have a few minutes to spare. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3d
During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
iPhone 12 pro with iOS 26.0 (23A5276f) App: https://developer.apple.com/documentation/wifiaware/building-peer-to-peer-apps We aim to use Wi-Fi Aware to establish file transfer between Android and Apple devices. Apple will act as the Publisher, and Android will act as the Subscriber. According to the pairing process outlined in the Wi-Fi Aware protocol (Figure 49 in the Wi-Fi Aware 4.0 specification), the three PASN Authentication frames have been successfully exchanged. Subsequently, Android sends the encrypted Follow-up PMF to Apple, but the Apple log shows: Failed to parse event. Please refer to the attached complete log. We request Apple to provide a solution. apple Log-20250808a.txt
10
0
320
Aug ’25
File download not working in Xcode 26.0 RC
Hello Apple Developer Community, I'm experiencing an issue with file download functionality in the iOS Simulator after updating to Xcode 26 RC (Build 17A321). Issue Description: When attempting to download files in the iOS Simulator via Safari, the download prompt appears correctly, but after tapping the 'Download' button, files are not being saved to the Files app. The download appears to do nothing with no error message, no indication of failure, but the file simply doesn't appear in Downloads or anywhere in the Files app. Environment: Xcode Version: 26.0 RC (17A321) iOS Simulator Version: 26.0 RC (23A339) Device Simulated: iPhone Air Steps to Reproduce: Open Safari in the iOS Simulator Navigate to a downloadable file (PDF, ZIP, etc.) Tap to initiate download Download prompt appears as expected Tap the 'Download' button Check the Files app → Downloads folder (empty) Expected Behavior: Files should download normally as they do on physical devices and as they did i
3
0
81
3d
App getting stuck after active from background
I got users feed back, sometimes they seem the launch screen after active from background, and the launch screen show more longer than the cold launch. I check the app's log, when this issue happens, it displays a view controller named 'STKPrewarmingViewController', and disappears after about 5 seconds. And form the normal users, app don't have same behavior. It seems app need prewarming after back from background, why? Devices System version: iOS 18.4, app build with Xcode 16. How to fixed this issues? Thanks!
1
0
172
3d
Reply to Provisioning problem
Was struggling for hours before discovering this thread. The issue for me was for literally any app i tried to upload, not just one specific app. I did discover a workaround. WORKAROUND: Go to Certificates, Identifiers & Profiles Create a profile that specifically targets your app bundle identifier create the profile, download it disable automatic profile management in xcode under Signing & Capabilities Import newly downloaded profile worked for me :)
3d
Reply to Siri Shortcut Passes NSUserActivity Object Twice
Hi Ed, Thanks for the detailed response. I’d like to clarify one point: my app is still using the UIApplicationDelegate lifecycle and not the scene-based lifecycle. Could this duplication be related specifically to using the AppDelegate lifecycle rather than the scene lifecycle? If so, is there a recommended way to handle or prevent the duplicate delivery without migrating to the scene lifecycle? Thanks in advance for your guidance.
3d
Reply to iOS 26 Safari & WebView: VisualViewport.offsetTop not reset after keyboard dismissal, causing fixed elements misplacement
@DTS Engineer I just upgraded Xcode to version 26 and downloaded the official release of iOS 26. The issue with fixed elements being incorrectly positioned after the keyboard has been pulled up within a WebView still exists. I hope Apple can intervene and address this as soon as possible. The changes in iOS 26 have affected web pages across the entire internet.
Topic: Safari & Web SubTopic: General Tags:
3d
StoreKit2: appAccountToken in purchase() always returns first value instead of updated UUID
Hello, I’m experiencing an issue with StoreKit 2 when passing a new appAccountToken for each purchase request. Case-ID: 15948169 (for DTS reference) Description of the Problem When initiating a purchase, I generate a new UUID to use as the appAccountToken: let serverTransactionId = UUID() let options: Set = [ .appAccountToken(serverTransactionId) ] let result = try await product.purchase(options: options) Expected Behavior: Each new purchase should return the updated appAccountToken that I pass into the purchase options. Actual Behavior: The payload response after success always contains the same appAccountToken from the very first transaction. It ignores subsequent UUIDs I pass and keeps reusing the original one. This causes issues because the same identifier is being reused across multiple transactions, making it difficult to map purchases to the correct user session. Steps to Reproduce Generate a fresh UUID using UUID(). Pass it as .appAccountToken when calling purchase(). Complete the transaction
2
0
73
4d