Hello, I am currently developing an application using SensorKit to retrieve visit data. While the data retrieval works smoothly on one iPhone (iPhone 14, iOS 18.0.1), it fails on other devices, including: iPhone 15 Pro Max with iOS 18.1 Beta Another iPhone 14 with iOS 18.0 I’ve verified that the entitlements are configured properly, and the app has the necessary SensorKit visit permissions across all devices. Despite these steps, only one of the phones is able to retrieve the visit data correctly. Is there any minimum hardware requirement or compatibility issue with certain models or configurations that I should be aware of for using SensorKit visits? Any guidance or insight would be greatly appreciated! Thank you.

Issue When triggering an App Intent using assistant schemas from Apple Intelligence (voice or text) the App opens without prompting for search criteria. How to repeat This can be repeated in the example provided by Apple here: https://developer.apple.com/documentation/appintents/making-your-app-s-functionality-available-to-siri Download the sample code Build and run on Xcode 16.1 beta 3 Target iPhone 15 Pro Max on iOS 18.1 beta 7 Trigger Apple Intelligence Enter prompt: "Search AssistantSchemasExample" Expected behaviour Apple Intelligence should prompt the user for the criteria and provide this to the App so that the experience is seamless for the end-user. Otherwise Assistant Intents are nothing more than deep links to search screens. Notes The example uses @AssistantIntent(schema: .photos.search) intent. And I've found the issue is also present in other search intents: @AssistantIntent(schema: .system.search) @AssistantIntent(schema: .browser.search) Questions Has anyone managed to get the prompt to appear? Will this only function on iOS 18.2?

Under iOS 18.0.1, I can't do any development that uses HTTPS, because I can't authorize my generated certificates on my phone. This was not a problem in the past. Normally you AirDrop a root certificate authority to your phone, install the "profile" for it, and then trust it in Settings / General / About / Certificate Trust Authority. Then you can connect to another server on your network that's using the accompanying certificates. But after sucessfully installing two profiles on my phone, neither shows up in Certificate Trust Authority. Anybody else seeing this? This problem, in combo with this one (which prevents running on my Mac as an iPad app) has completely halted my project. I've found reports of this problem that blamed an empty "common name" field in the certs, but that field is populated in both of these.

I've noticed delays with the Live Caller ID Lookup feature, taking around 3 to 6 seconds to complete, even on repeated lookups. This seems odd since there's no server activity during these repeats, suggesting the information might be coming from a cache. Most of the time, it’s fast, but there are cases when it's unexpectedly slow, and I haven’t quite figured out the pattern yet. Is anyone else seeing this issue? FB number FB15372765 - with sysdiagnose and video demonstrating the delay.

I am working on capturing 48MP images using the iPhone 16 Pro Max with the Ultra-wide camera. I’ve updated the code to capture the maximum supported dimensions with the following snippet: if #available(iOS 16.0, *) { photoOutput.maxPhotoDimensions = device.activeFormat.supportedMaxPhotoDimensions.last! photoSettings.maxPhotoDimensions = .init(width: 5712, height: 4284) } However, I’m still not getting the expected results. My goal is to capture 48MP images, and I want to confirm if the Ultra-wide camera supports this resolution or if I’m missing any other configuration. Any guidance would be appreciated!

In my React Native mobile application, we are experiencing app termination issues on a few devices (iPhone 13 & 14). We have implemented Firebase Crashlytics, we are getting crashes logs but we are not receiving any logs for app terminations when app terminates due to memory leak or terminates by OS. Could you please suggest a way to log app terminations or recommend any other platform where we can log such events? Alternatively, do you have any suggestions on how to resolve app termination issues?

Xcode Version 16.0 (16A242d) [_NSFullScreenMenuBarCompanionController layoutTitlebarViews] last stack error :Thread 1: EXC_BAD_ACCESS (code=1, address=0x6b414b754e0) A bad access to memory terminated the process. Presenting a fullscreen viewController will cause crash in TabBarController when running iOS App in Mac(Designed by iPad) A demo gonna recreate this crash. Demo is in attachment in Feedback issue (FB15183434). Or you can try yourself. Create a TabBarController Try to present a view controller as fullscreen mode. Crash will be occurred. #warning(": Bug is here when presenting a fullscreen view controller from a tab bar managed view controller,") let vc = UIViewController() vc.modalPresentationStyle = .fullScreen present(vc, animated: true)

I developed my app with React-Native-CLI, version 0.67.2. I use Xcode 16 on MacOS Sequoia 15.0.1 It builds and runs fine on any simulator, iOS 17 or iOS 18. As soon as I build it for my iPhone 12 iOS 17.6.1 or archive, it throws this error "Command PhaseScriptExecution failed with a nonzero exit code" at the last time. It actually starts the Metro. I made my iPhone into developer mode. Paired it with MacOS. The thing I don't get why it doesn't work on my iPhone when it works fine on simulators. It doesn't even archive. Anyone encountered something like this in the past?

I'm embedding PHPickerViewController in my application with a little bit of other chrome around it to provider context about how to upload. But the fact that the controller has a translucent background to the videos when scrolling, and the rest of my UI doesn't, looks bad. Is there a way to customize the controller to either: have the translucent background extend further than the extents of it, or remove the translucent background entirely?

I was trying to debug an issue with entry point not being found on iOS 18.0 simulator and device(iPhone 14 Pro) with no success since the Xcode console output just prints No entry point found. Checked '(null)'. Later when I tried to use iOS 15.0 Simulator of iPhone 13 to see if it makes a difference, I could see more verbose messages from the loader trying to look for entry points and was able to pin point the root cause of the issue. Nothing was changed in the project settings, env variables or anything except switching to iOS 15.0 simulator from iOS 18.0 simulator, so I don't think it is environment issue or project configuration issue. The absence of detailed logging got me stuck on this issue for sometime. The same issue (minimal logging) was observed on iOS 17.4 simulator as well but is not present on iOS 15.0. iOS 18.0 Log: No entry point found. Checked '(null)' iOS 15.0 Log: 2024-10-13 13:31:17.970323+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib relative path 2024-10-13 13:31:17.970533+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Found debug dylib relative path string SideStore.debug.dylib 2024-10-13 13:31:17.970560+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib entry point name 2024-10-13 13:31:17.970583+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No debug dylib entry point name defined. 2024-10-13 13:31:17.970615+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking up debug dylib install name 2024-10-13 13:31:17.970646+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Found debug dylib install name string @rpath/SideStore.debug.dylib 2024-10-13 13:31:17.970672+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking for Previews JIT link entry point. 2024-10-13 13:31:17.971776+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No Previews JIT entry point found. 2024-10-13 13:31:17.971797+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Gave PreviewsInjection a chance to run and it returned, continuing with debug dylib. 2024-10-13 13:31:17.971816+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Looking for main entry point. 2024-10-13 13:31:17.971846+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Opening debug dylib with '@rpath/SideStore.debug.dylib' 2024-10-13 13:31:17.971935+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] Debug dylib handle: 0x205c2d2a0 2024-10-13 13:31:17.971969+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No entry point found. Checking for alias. 2024-10-13 13:31:17.972368+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No alias entry point found. Falling back to look up entry point name 'main' 2024-10-13 13:31:17.972926+0530 SideStore[62559:1632528] [PreviewsAgentExecutorLibrary] No entry point found. Checked '(null)' Questions: What is the difference between iOS 15 and > iOS 17.4 Is this a bug or expected behavior? if so how do I get back logging as in iOS 15.0 on iOS 18.0 (need detailed logging from the loader) which exact version of IOS was this change/bug got introduced?

I have installed iOS 18 to my iPhone 13 Pro Max and now the future that can minimise the video call when turned on Picture in Picture mode dose not work anymore in telegram, while the rest of the apps are working fine. if anyone know how to fix this please reply.

When I create a new iOS playground in Xcode 16.0 with an iOS 18.0 SDK installed, I cannot use some of the new features such as the new way for programming tab layouts. When I just use an Xcode project, these features work as expected. In a playground, I get errors saying "x is only available in iOS 18.0 and later". I have noticed this for more than just this feature. Is there some way I can force the playground to run with iOS 18 as I have the appropriate SDKs installed?

In my app, most views use List for all tabs. However, due to a custom design, I switched one tab to use ScrollView. I quickly noticed that, unlike List, which applies default padding around the entire view and its items, ScrollView has no such built-in padding. Initially, I assumed that applying a simple .padding(.horizontal) would give the items in ScrollView the same padding as List, but that wasn’t the case. It turns out List adjusts its padding based on screen size. For larger iPhones, like the Plus and Pro Max models, List uses 20px padding, whereas regular-sized iPhones (including the Pro) use 16px. This discrepancy creates an inconsistency when trying to replicate the same padding behavior with ScrollView. Thus, my question how can I apply this conditional padding and/or if there's an API to get the value of the default padding used by List? Also, there’s a difference in padding depending on whether you run the app in the simulator or on a physical device, even if both the simulator and the physical device are the same model and iOS version. iPhone 13 iOS 17.4 Simulator: iPhone 13 iOS 17.4 Physical device: As you can see simulator for iPhone 13 has what I assume 20px paddings for List and List items. So the default padding applied to items in ScrollView is misaligned. iPhone 15 Pro Max iOS 18.0 Physical device and Simulator: In summary, it seems that simulators consistently apply 20px padding for List, while physical devices adjust between 20px and 16px based on screen size. Meanwhile, .padding(.horizontal) always applies 16px and doesn’t dynamically switch to 20px on larger screens. Any thoughts how to work around this? Code example: struct ContentView: View { var body: some View { VStack(spacing: 0) { ScrollView { ForEach(0..<50) { i in Text("Item #\(i)") .padding(.horizontal) .frame(maxWidth: .infinity, alignment: .leading) .background(.orange) .padding(.horizontal) } } List { ForEach(0..<50) { i in Text("Item #\(i)") .background(.green) } } } } }

When you zoom in photo and swipe to another photos as usual. It would show the other photos in the background where should be black. it happened even after updated to the latest

With iOS 18.1 having call recording out of the box, is it now possible to build apps that can record calls? I could not find anything in the swift ios docs yet.

Is there any improvement in dynamic island?

With this sample code here: import SwiftUI struct ContentView: View { var body: some View { Text("Hello world") .hoverEffect(isEnabled: true) } } private extension View { func hoverEffect(isEnabled: Bool) -> some View { if #available(iOS 17.0, *) { // VisionOS 2.0 goes in here? return self .hoverEffect(.automatic, isEnabled: isEnabled) } else { return self } } } You would expect if the destination was visionOS it would go into the else block but it doesn't. That seems incorrect since the condition should be true if the platform is iOS 17.0+. Also, I had this similar code that was distriubted via a xcframework and when that view is used in an app that is using the xcframework while running against visionOS there would be a runtime crash (EXC_BAD_ACCESS). The crash could only be reproduced when using that view from the xcframework and not the local source code. The problem was fixed by adding visionOS 1.0 to that availability check. But this shouldn't have been a crash in the first place. Does anyone have thoughts on this or possibly an explanation? Thank you!

There's been an article where it says Apple/iOS apps can use the FONT_FAMILY='System' which is defaulted to use San Francisco (SF font). Is this valid Fontfamily to use? If yes, is it open source to use?

We convert a .onnx file to mpsgraphpackage for iOS deploymentPlatform with command “Mpsgraphtool convert -deploymentPlatform iOS -minimumDeploymentTarget17.0.0 model.onnx -path .” When open output.mpsgraphpackage with Xcode16, there are only “generic” and “ Apple M2(MTLDevice)” options in the “Device” selection list. Cannot find any option for iOS device. How can we view mpsgraph compiled for iOS platform? We use Xcode16 on a MacBook Pro M2 with macOS 15.

Hello everyone, I'm working on an iOS application using Objective-C and UITabBarController. My app has more than 5 tabs, so the additional tabs are placed under the "More" tab. However, I've encountered an issue specific to iOS 18 where the first item in the "More" tab does not show up properly. This issue does not occur in iOS 17 or earlier versions. Here's my setup method: (void)mainTabbarSetUp { NSMutableArray *tabItemArray = [NSMutableArray array]; UIViewController *viewController1, *viewController2, *viewController3, *viewController4, *viewController5, *viewController6, *viewController7; UINavigationController *navviewController1, *navviewController2, *navviewController3, *navviewController4, *navviewController5, *navviewController6, *navviewController7; viewController1 = [[UIViewController alloc] init]; navviewController1 = [[UINavigationController alloc] initWithRootViewController:viewController1]; navviewController1.tabBarItem.title = @"Watch List"; navviewController1.tabBarItem.image = [UIImage imageNamed:@"tab_icn_watchlist"]; [tabItemArray addObject:navviewController1]; // Similarly adding other view controllers... viewController6 = [[UIViewController alloc] init]; navviewController6 = [[UINavigationController alloc] initWithRootViewController:viewController6]; navviewController6.tabBarItem.title = @"Cancelled"; navviewController6.tabBarItem.image = [UIImage imageNamed:@"tab_icn_cancelled"]; [tabItemArray addObject:navviewController6]; self.mainTabBarController.viewControllers = tabItemArray; } What I've Tried: Verified that each view controller is correctly initialized and assigned to a UINavigationController before being added to the tab array. Logged the contents of the moreNavigationController to confirm that it contains the correct view controllers. Tested by reducing the number of view controllers to less than 5, and the issue does not occur. Ensured that all UINavigationControllers are configured consistently (e.g., translucency, bar style, etc.).