iOS is the operating system for iPhone.

Posts under iOS tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

Screen Sleep Issue When Removing Vision Pro
Hello VisionOS Developer Community, I am currently working on a demo application for VisionOS, tailored for the Vision Pro. In my application, I have implemented a feature to prevent the screen from sleeping using the following code: UIApplication.shared.isIdleTimerDisabled = true This works perfectly on iOS, ensuring the screen remains active regardless of other system settings. However, I've run into a snag with VisionOS. Even with isIdleTimerDisabled set to true, the screen still sleeps when I take off the Vision Pro.
0
0
147
2w
Instruments of Xcode not showing correct memory allocation on the latest version of iOS for PacketTunnelProvider Process
We have observed for a few months that the Instruments tool in Xcode does not show correct memory allocation for the PacketTunnelProvider process on iOS 17. The memory allocation does not exceed 6-7 MB, which is not the case with iOS 16 or 15. Additionally, Instruments crashes the PacketTunnelProvider process after profiling for a few minutes. Please note that I am not running Xcode in debugger mode for the PacketTunnelProvider process along with instruments, as this is a known issue that causes the PacketTunnelProvider to be killed when both Instruments and the Xcode debugger are running. Is anyone else facing this issue and have a workaround?
0
1
168
2w
About cpu_resource_fatal
PLATFORM AND VERSION iOS Development environment: Xcode 15.0, macOS 14.4.1, Objective-C Run-time configuration: iOS 17.2.1, DESCRIPTION OF PROBLEM What is the general approach to analyzing cpu_resource_fatal.ips? Is there a standard way to analyze it? (Instruments are not available in this analysis, because this is only occurs on the customer's iPhone.) Also, can this file be symbolicate? Attachment file is a sample ips file. FjSoftPhone.cpu_resource_fatal-2024-06-21-150321.ips
1
0
173
2w
Apple TestFlight review rejected
Reason provided by the reviewer: We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. Review device details: Device type: iPad Air (5th generation) and iPhone 13 mini OS version: iOS 17.5.1 apple crash log However, the app we downloaded through TestFlight runs normally on all systems without any issues. May I ask what could be the reason for this?
1
0
201
3w
Crash when presenting UIPrintInteractionController on iOS 16
Starting iOS 16 seeing some crashes related to pdf printing in the crash reporter. It looks like the issue is not so frequent. Also, I'm unable to reproduce the crash. Looks like the app crashes when the print preview dialog is opening. According to crash reports, there are some crashes on different iOS 16 versions: 16.0.0, 16.0.2, and 16.0.3. Printing code: let printInfo = UIPrintInfo.printInfo() printInfo.jobName = "Printing Job Name" self.printViewController = UIPrintInteractionController.shared self.printViewController?.printInfo = printInfo self.printViewController?.printingItem = pdfURL self.printViewController?.present(from: barButtonItem, animated: true) { (controller, completed, error) in self.printViewController = nil } Stack trace: compare_key + 4 (CGPDFObject.c:134) bsearch + 68 (bsearch.c:70) CGPDFDictionaryGetUnresolvedObject + 68 (CGPDFDictionary.c:153) CGPDFDictionaryGetObject + 44 (CGPDFDictionary.c:172) CGPDFDictionaryGetDictionary + 44 (CGPDFDictionary.c:284) get_pages_dictionary + 68 (pdf-reader.c:410) pdf_reader_get_number_of_pages + 76 (pdf-reader.c:557) -[UIPrintPreviewPageFetcher fetchNumberOfItems] + 76 (UIPrintPreviewPageFetcher.m:115) -[UIPrintPreviewViewController collectionView:numberOfItemsInSection:] + 32 (UIPrintPreviewViewController.m:482) -[UICollectionViewData _updateItemCounts] + 220 (UICollectionViewData.mm:335) -[UICollectionViewData isIndexPathValid:validateItemCounts:] + 52 (UICollectionViewData.mm:348) -[UICollectionViewData validatedGlobalIndexForItemAtIndexPath:] + 36 (UICollectionViewData.mm:778) -[UICollectionView _cellForItemAtIndexPath:] + 108 (UICollectionView.m:7112) -[UICollectionView _endItemAnimationsWithInvalidationContext:tentativelyForReordering:animator:collectionViewAnimator:] + 1384 (UICollectionView.m:9357) -[UICollectionView _updateRowsAtIndexPaths:updateAction:updates:] + 396 (UICollectionView.m:9104) -[UICollectionView reloadItemsAtIndexPaths:] + 52 (UICollectionView.m:9124) -[UIPrintPreviewViewController reloadVisibleItems:] + 256 (UIPrintPreviewViewController.m:568) __63-[UIPrintPreviewViewController updatePdfURL:options:completed:]_block_invoke_2 + 44 (UIPrintPreviewViewController.m:305) __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 24 (NSOperation.m:1545) -[NSBlockOperation main] + 104 (NSOperation.m:1564) __NSOPERATION_IS_INVOKING_MAIN__ + 16 (NSOperation.m:2189) -[NSOperation start] + 708 (NSOperation.m:2206) There is full stack trace I got from the Organizer Thanks!
13
5
3.7k
3w
Xcode beta 15.0 beta 2 cannot connect to iPhone SE running iOS 17.0 beta
macOS Version 13.4.1 (Build 22F82) Xcode 15.0 (22181.22) (Build 15A5161b) iPhone SE running iOS 17.0 beta I have a test device (iPhone SE) with iOS 17 beta installed. I am using a cable to connect it to my MacBook. Within Xcode beta, I am using the "Devices and Simulators" dialog. Attempting to "connect" the device fails repeatedly with the following message: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Error mounting image: 0xe8000106 (kAMDMobileImageMounterCredentialsFailed: AppleConnect authentication failed or was cancelled.) User Info: { DDIPath = "/Users/***/Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; DVTErrorCreationDateKey = "2023-06-23 17:08:18 +0000"; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } -- Error mounting image: 0xe8000106 (kAMDMobileImageMounterCredentialsFailed: AppleConnect authentication failed or was cancelled.) Domain: com.apple.mobiledevice Code: -402652922 User Info: { FunctionName = AMDeviceRemoteMountPersonalizedBundle; LineNumber = 2108; } -- AMAuthInstallRequestSendSync failed: 22 (kAMAuthInstallErrorAppleConnectAuthFailed) Domain: com.apple.mobiledevice Code: -402652922 User Info: { FunctionName = "-[PersonalizedImage mountImage:]"; LineNumber = 2005; } -- I also see the following error from the phone's console: Sending response: { DetailedError = "Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to copy personalization manifest.\" UserInfo={NSLocalizedDescription=Failed to copy personalization manifest., NSUnderlyingError=0x7a6a07b80 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to retrieve personalization manifest: Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"Failed to find a cached manifest (im4m) for variant DeveloperDiskImage (personalization required).\" UserInfo={NSLocalizedDescription=Failed to find a cached manifest (im4m) for variant DeveloperDiskImage (personalization required)., NSUnderlyingError=0x90ab04240 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 \"/private/var/run/mobile_image_mounter/DeveloperDiskImage/B5A2B06AE07F3A280BC168DCAFE0D3BADD8CFCAA017BE5C735299D5398807133F23C61593439B0B93C4B772168E8F711.im4m does not exist.\" UserInfo={NSLocalizedDescription=/private/var/run/mobile_image_mounter/DeveloperDiskImage/B5A2B06AE07F3A280BC168DCAFE0D3 I have tried the usual things: Restarting Xcode. Restarting the iPhone. Logging in/out from iCloud on the iPhone. Logging in/out of Apple Developer within Xcode. Restarting my MacBook. Burning sage and making an incantation.
9
1
4.4k
3w
PingFang.ttc font file is missing in iOS 18.0
I'm an iOS developer, and I've been testing our app in iOS 18.0 Beta. I noticed that there's a problem with the font rendering, and after troubleshooting, I've found out that it's caused by the removal of the PingFang.ttc font in 18.0. I would like to ask the reason for removing this font file and which font should be used to display Chinese in the future? My test device is an iPhone 11 Pro and the system version is iOS 18.0 (22A5297). I have also tested Beta 1 and it has the same issue. In previous versions of the system, the PingFang font is located in this directory /System/Library/Fonts/LanguageSupport/PingFang.ttc. But in iOS 18.0, the font file in this directory has become Kohinoor.ttc, and I've tested that this font can't display Chinese either. I traversed the following system font directories and could not find the PingFang.ttc font file. /System/Library/Fonts/AppFonts /System/Library/Fonts/Core /System/Library/Fonts/CoreAddition /System/Library/Fonts/CoreUI /System/Library/Fonts/LanguageSupport /System/Library/Fonts/UnicodeSupport /System/Library/Fonts/Watch Looking for answers, thanks for the help!
1
1
326
3w
IOS 18 Beta 2 bug fix
After a week of testing iOS 18. iPhone XS keeps randomly up and down cellular network which shows low signal /no service/ hig signal after I use it for a few minutes. second bugs is keyboard switching , sometimes don’t work auto predictive and auto capitalisation in keyboard. Reported this issue through feedback assistant. Please fix this bug in next iOS 18 beta.
6
2
2.2k
3w
1 week Free Trial before subscription
Hello there, i already looked for a similar post but nothing suits me or the posts were way too old and deprecated. I want to give a 1 week free trial to my customer before they sign the monthly auto-renewable subscription. My questions are: May I set a free trial through code and then show the Apple Subscription page after the trial finished? Or shall I do everything in-Apple (so Apple manages the free trial and consequently shows the subscripion page)? Where is the option to make a subscription free for the first week? I saw some posts but now i can't find the 0,0€ option, as now everything start from 0,25€ Thank you for your time, any help will be very much appreciated
4
0
429
3w
Call history problems after iOS 18 beta update
I've 14-Pro and I recently did update to "iOS 18 beta" using beta channel. However, the first I noticed was a deleted call-history... After several tries (using tips from forums), nothing showed up. Finally, I did reset all and reverted back to "17.5.1" and used the last iCloud backup (right before iOS 18 upgrade). Call history is back, however it is limited to "only 1-month" back in time! Why? I've 2 TB iCloud storage, why my call history is gone why? I keep backup of everything, and call-history contains very important details as well. Please help in getting back my data asap.
1
1
290
3w
Unfinished transactions not being emitted on start of app
I'm using the iOS simulator with a StoreKit configuration file. I can see that there have been transactions while the app has been closed, but my StoreKit 2 listener is never called with those updates to be able to finish them When I open my app from a cold start. I've added a listener on application(_:didFinishLaunching:launchOptions:) like this: func startObservingTransactions() { task = Task(priority: .background) { for await result in Transaction.updates { if case .verified(let transaction) = result { await transaction.finish() } } } } But the Transaction.updates loop never gets called (have added breakpoints to check). It's only ever called when a purchase is made, or subsequent transaction renewals when the app is open. Only then it will get the previously unfinished transactions. Steps to reproduce: Create an app with a StoreKit config file (with sped up transactions) to purchase an item Make a purchase then quit the app Wait for a bit for more transactions to be made while the app is closed. Open the app from a cold start and none of the transactions will be finished by the listener in your app. Cancel the subscription via the transaction manager. Close and open the app from a cold start. The first transaction will be finished by the listener but none of the others will be. In Apple's docs it says If your app has unfinished transactions, the listener receives them immediately after the app launches Why is this not the case?
14
2
3.4k
3w
SwiftData ModelContext Fetch Crashing
I'm currently using Xcode 16 Beta (16A5171c) and I'm getting a crash whenever I attempt to fetch using my ModelContext in my SwiftUI video using the environment I'm getting a crash specifically on iOS 18 simulators. I've opened up a feedback FB13831520 but it's worth noting that I can run the code I'll explain in detail below on iOS 17+ simulator and devices just fine. I'm getting the following crash: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'The specified URI is not a valid Core Data URI: x-coredata:///MyApp/XXXXX-XXXXX-XXXX-XXXX-XXXXXXXXXXXX' It's almost as if on iOS18 SwiftData is unable to find the file on the simulator to perform CRUD operations. All I'm doing in my project is simply fetching data using the modelContext. func contains(_ model: MyModel, in context: ModelContext) -> Bool { let objId = palette.persistentModelID let fetchDesc = FetchDescriptor<MyModel>(predicate: #Predicate { $0.persistentModelID == objId }) let itemCount = try? context.fetchCount(fetchDesc) return itemCount != 0 }
4
4
470
3w
IOS 18 Bugs
I downloaded IOS 18 beta on my 14 pro max and here’s a list of bugs or issues I’ve encountered so far: —Phone completely freezing after locking and unlocking —Calls glitching out and causing phone to crash —FaceID shows that the phone is unlocked but still have to put in the password —Phone taking multiple minutes to turn back on after hard reset —Randomly crashing and restarting (even when not using the phone) —Unlocking phone and being unable to see bottom row of apps or press anything on the screen —Widgets not loading (accompanies the freezing screen and faceID and unlocking not working correctly)
1
0
326
3w
iOS 17 apps still require 5.5" iPhones screenshots?
I find odd that the App Store Connect still requires 5.5" iPhone screenshots of the iPhone 8 Plus, given that this specific phone is no longer supported by the latest release: iOS 17. I am well aware that the iPhone SE still has a similar screen ratio, and that it is still being supported by iOS 17, but it doesn't have the same pixel requirements (1242 x 2208), which means that in order for my app to be even reviewed (which is an iOS 17+ exclusive), I'm gonna have to create images that will then be upscaled to the right dimensions. Am I missing something here, or is it Apple who missed this detail?
32
21
9.9k
3w