In iOS18, Not able to use the UITabBarControllerDelegate.tabBarController(:didSelectTab:previousTab:) function. Since it have duplicate parameter name for didselectTab and previousTab , we're getting Invalid redeclaration of 'tab' error.

IOS 18 below FFmpeg subtitle synthesis log [Parsed_subtitles_0 @ 0x301b37650] Using font provider fontconfig [Parsed_subtitles_0 @ 0x301b37650] fontselect: (PingFangSC-Semibold, 400, 0) -> /System/Library/Fonts/LanguageSupport/PingFang.ttc, 8, PingFangSC-Semibold IOS 18 FFmpeg subtitle synthesis log [Parsed_subtitles_0 @ 0x303e825d0] Using font provider fontconfig [Parsed_subtitles_0 @ 0x303e825d0] fontselect: (PingFangSC-Regular, 400, 0) -> /System/Library/Fonts/Core/HiraginoKakuGothic.ttc, 10, . HiraKakuInterface-W4 [Parsed_subtitles_0 @ 0x303e825d0] Glyph 0x8FD9 not found, selecting one more font for (PingFangSC-Regular, 400, 0) [Parsed_subtitles_0 @ 0x303e825d0] fontselect: (PingFangSC-Regular, 400, 0) -> /System/Library/Fonts/Core/LastResort.otf, 0, LastResort In normal characters, there may be some garbled characters, such as 0x8FD9 mentioned in the log, corresponding to "这" Traditional Chinese and Simplified Chinese Normal font: Russian, Korean, Japanese, French, English, German IOS 18 below FFmpeg subtitle synthesis log fontselect: (PingFangSC-Semibold, 400, 0) -> /System/Library/Fonts/LanguageSupport/PingFang.ttc, 8, PingFangSC-Semibold IOS 18 FFmpeg subtitle synthesis log fontselect: (PingFangSC-Regular, 400, 0) -> /System/Library/Fonts/Core/HiraginoKakuGothic.ttc, 10, . HiraKakuInterface-W4 In iOS 18, the selected font has changed and instead of continuing to use PingFang.ttc, HiraginoKakuGothic. Has iOS changed the PingFang font directory, causing ffmpeg to be unable to use system fonts for subtitle synthesis

Hi, I'm writing because I've been trying to set the .standard map style to render as a globe on an iPhone 15 running iOS 17 when zoomed out similar to how it works in Apple Maps but can't find any resources on how to make that happen as every time it appears as a flat 2D map, much unlike the .hybrid and .satellite types. I found another thread on this forum a year ago where someone said .standard was bugged and couldn't become a globe, but I'm honestly quite surprised this issue hasn't been brought up more often.

There is definitely a glitch with the latest update of iOS 18 Beta4 with Google Maps in carplay mode. Google Maps on the car screen is almost responsive. It does not recognize your home or work address. While there might be a workaround to get to your destination. Use Siri to get directions, but speak the full address and tell it to give directions using Google Maps. For e.g. "Hey Siri, get me directions to "XX LOCATION" using Google Maps" You can use Apple Maps and Waze. But its hard for people to use another navigation app rather than using what they are used to. I find Google Maps really easy to use and handy, and now, with the latest update of Google Maps you can update live incidents, accidents, slowdowns and traffic reports from your dashboard

I have two feedback issues under Sequoia that are fairly major features. FB14105190: iPhone Mirroring shows only a white rectangle. FB13888947: VisionOS Mirroring drops connections after seconds. Both these issues are features I use (VisionOS Mirroring) or would use (the other) if I could. On a suggestion from a colleague I booted in Safe Mode and the issues went away and everything worked as it should. I've sent this upline to Feedback. But am curious what I can do to diagnose this further. Maybe locate a culprit. In the olden days, the extension parade let you know what was loaded. My kextstatus shows nothing different. Is there anything else I can explore to find this? Thanks.

ViewControllers for the 8th and higher tabs are not displayed in the elevated Tab Bar. However, I am able to select these tabs both in the Tab Bar and the side bar. func setTabs(){ let colors = [UIColor.red,.systemGray6,.green,.systemMint,.cyan,.yellow,.blue,.magenta] var tabs = [UITab]() let range = 0...10 for index in range { if #available(iOS 18.0, *) { let tab = UITab(title: "Tab_\(index)", image: UIImage(systemName: "globe"), identifier: "tab__\(index)", viewControllerProvider: {tab in let vc = UIViewController() vc.view.backgroundColor = colors[index%colors.count] return vc }) tabs.append(tab) } } tabbarController.setTabs(tabs, animated: true) }

In our application, we have a button on click of which we are creating a new WKWebView instance and before loading the url clearing website data using WKWebsiteDataStore removeDataOfTypes method to remove allWebsiteDataTypes. The problem is when app is relaunched, the login session remains active whereas the same code ends session and we get login page when the same button is clicked when app is in running mode and not killed. Any suggestion on how to debug or what's going incorrect is really appreciated. Let me know incase of query. Thanks!

Which framework or low level module can be used to allow a swift app to take a screenshot of the homes creen of an iOS device connected to the USB port? I have seen several commercial apps that can to it, so there must be a module or framework they are using (and is not libimobile3, it must be apple native code)

The new Home Screen customization forces automatically darkened app icons when dark mode is selected. It’s not possible to have the previous behavior where UI elements (like menus, pop-ups, and widgets) are dark and app icons retain their original appearance. While widgets can individually be set back to dark mode, that’s tedious, and it doesn’t cover other elements. There should be an option to toggle dark icons separately from the other elements (because, to be blunt, quite a few dark mode icons look really bad). FB14476705

When to expect beta 5. Not to many changes between beta 3 and 4. Hoping that beta 5 will deliver more updates

I've followed the instructions to configure and launch a live caller id test service (https://swiftpackageindex.com/apple/live-caller-id-lookup-example/main/documentation/pirservice/testinginstructions) i.e. I've constructed a database, built and installed the PIRService etc. Additionally I have created a test app with a Live Caller ID Extension. The problem I'm facing is when turning on the Live Caller ID feature on an iPhone (the Settings|Apps|Phone|Call Blocking & Identification|Live CallerID Lookup switch) with iOS 18 Beta 4 is the phone logs: "The request timed out." UserInfo={NSLocalizedDescription=The request timed out., NSErrorFailingURLKey=http://MacBook-Pro.local:8080/.well-known/private-token-issuer-directory The configuration notes say: "When running things locally on your Mac, and your testing device is on the same network, then you can use mDNS to let the device find your Mac. Let’s assume that your Mac’s hostname is Tims-MacBook-Pro.local. Then we should use the following value for the URLs: http://Tims-Macbook-Pro.local:8080. Thanks to the mDNS protocol your device should be able to resolve your hostname to the actual IP address of your Mac and make the connection." My Mac hostname is "MacBook-Pro" therefore the Live Caller ID Extension is configured as: LiveCallerIDLookupExtensionContext( serviceURL: URL(string: "http://MacBook-Pro.local:8080")!, tokenIssuerURL: URL(string: "http://MacBook-Pro.local:8080")!, userTierToken: Data(base64Encoded: "BBBB")! ) And the service-config.json is configured as: { "issuerRequestUri": "http://MacBook-Pro.local:8080", "users": [ <snip> (I've also tried excluding the issuerRequestUri as the instructions say "This value can be omitted from the configuration. Setting this explicitly will not be required for devices using iOS 18.0 beta 4 or later.") And the PIR Service is started on the Mac as: PIRService --hostname 0.0.0.0 service-config.json And it starts and runs. The iPhone and Mac are on the same Wifi network and connected by usb cable. As far as I can tell, everything has been set up in accordance with the Testing Live Caller ID instructions, yet I get the error when attempting to enable the extension on the iPhone. Is there something missing/incorrectly configured?

I want to achieve Fold animation when the user scrolls UICollectionView. I have UICollectionView with full-screen size cell and vertically scrolling with paging enabled. For that I've created sub-class of UICollectionViewFlowLayout which is as described below. class FoldingFlowLayout: UICollectionViewFlowLayout { private let logger = Logger(subsystem: bundleIdentifier, category: "FlowLayout") override func prepare() { super.prepare() scrollDirection = .vertical minimumLineSpacing = 0 minimumInteritemSpacing = 0 } override func layoutAttributesForElements(in rect: CGRect) -> [UICollectionViewLayoutAttributes]? { let attributes = super.layoutAttributesForElements(in: rect) attributes?.forEach { attribute in transformLayoutAttributes(attribute) } return attributes } override func shouldInvalidateLayout(forBoundsChange newBounds: CGRect) -> Bool { return true } private func transformLayoutAttributes(_ attributes: UICollectionViewLayoutAttributes) { guard let collectionView = collectionView else { return } let contentOffsetY = collectionView.contentOffset.y let cellOffsetY = attributes.frame.origin.y - contentOffsetY let cellHeight = attributes.frame.height var transform = CATransform3DIdentity transform.m34 = -1.0 / 500.0 // Apply perspective if cellOffsetY < cellHeight && cellOffsetY > -cellHeight { let angle = (cellOffsetY / cellHeight) * .pi / 2 transform = CATransform3DRotate(transform, angle, -1, 0, 0) attributes.transform3D = transform attributes.alpha = 1.0 - (abs(cellOffsetY) / cellHeight) } else { attributes.transform3D = CATransform3DIdentity attributes.alpha = 1.0 } } } But this is not working as I expected. I want to create replica of this kind of animation. What am I missing here?

Hello, I have an iOS app for which I've received a number of similar crash reports over the last few months. Despite a lot of effort, I haven't been able to replicate the crash myself and I'm finding it difficult to diagnose. The main view of the app loads a list of items from Core Data using @FetchRequest and looking at the logs it appears to me that this is the most likely source of the crash as the call stack includes SwiftUI 0x19c78c368 FetchRequest.update() + 472 (FetchRequest.swift:406). It also appears as if this happens on launch as the crash times and launch times are always very similar. I've attempted lots of things to try and replicate the crash, such as launching the app a lot of times, creating lots of items so that the fetch request has a lot of data to retrieve, performing any other database related actions in the app immediately after launch to try and drive out any concurrency issues and simulating degraded thermal and network conditions for the device. I've included a sample crash report, I'd be very grateful if anyone has any suggestions for diagnosing the issue. Crash Report

I have been using the iOS 18 public beta on my iPhone XR for the past 3-4 days, and I frequently play a popular competitive game called “Free Fire.” I’ve noticed an issue while playing the game. Whenever I switch the game to the background for any reason, such as using another app or attending an incoming call, the game’s sound does not come back when I switch back to it. No matter what I do—whether switching the phone to silent mode and then back to normal or adjusting the volume—the sound won’t return. I have to restart the game, which is frustrating since I play this game a lot. I understand that this is a beta version, and some problems are expected, but I wanted to mention this issue here in case it can be resolved. apart from this i also tried a lot small stuff to solve the problem such as reinstalling the game , restarting the device , checking for new updates etc….. but none of them worked 😅

I have been using the iOS 18 public beta on my iPhone XR for the past 3-4 days, and I frequently play a popular competitive game called “Free Fire.” I’ve noticed an issue while playing the game. Whenever I switch the game to the background for any reason, such as using another app or attending an incoming call, the game’s sound does not come back when I switch back to it. No matter what I do—whether switching the phone to silent mode and then back to normal or adjusting the volume—the sound won’t return. I have to restart the game, which is frustrating since I play this game a lot. I understand that this is a beta version, and some problems are expected, but I wanted to mention this issue here in case it can be resolved. and i also tried some stuff like reinstalling the game or restrting the device or checking for new updates and all the small stuff that would fix this but nahhhh none of them worked 😅

I'm working on a mobile app that keeps crashing on launch since updating to iOS 18 Beta 3 and 4. The splash screen is shown and afterwards the app is crashing. The stack trace is very general and it's very hard to pinpoint where it's going wrong. Does someone experience the same behavior? The app was working on iOS 18 Beta 2. In the stack trace you can see that is goes wrong at OurObject. This is an object that inherits from UIStackView. Background information .NET8.0 iOS MVVMCross Stacktrace 2024-07-24 09:29:05.110 ***.iOS[9804:731403] Unhandled managed exception: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[OurObject initWithCoder:]: unrecognized selector sent to instance 0x300bb2ec0 Native stack trace: 0 CoreFoundation 0x000000019f0ba098 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 540824 1 libobjc.A.dylib 0x000000019c3c2698 objc_exception_throw + 76 2 CoreFoundation 0x000000019f1bf810 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 1611792 3 CoreFoundation 0x000000019f057728 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 137000 4 CoreFoundation 0x000000019f057050 _CF_forwarding_prep_0 + 96 5 UIKitCore 0x00000001a1b89308 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3756808 6 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 7 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 8 UIKitCore 0x00000001a1b85ec4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3743428 9 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 10 UIFoundation 0x00000001aab3b0bc D893DC98-0766-3DA9-BDD8-73614C11B808 + 82108 11 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 12 UIKitCore 0x00000001a1b894b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3757236 13 UIKitCore 0x00000001a1c6aa48 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4680264 14 UIKitCore 0x00000001a19836c4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1636036 15 UIKitCore 0x00000001a184c49c D2E47210-1C46-3CA7-BBC2-35021B146A13 + 361628 16 UIKitCore 0x00000001a226c7a8 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10979240 17 UIKitCore 0x00000001a226cc20 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10980384 18 UIKitCore 0x00000001a2a5baa0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 19298976 19 UIKitCore 0x00000001a194b590 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1406352 20 UIKitCore 0x00000001a1bf2ab4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4188852 21 UIKitCore 0x00000001a18047b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 67508 22 QuartzCore 0x00000001a0b3a6d8 EC26DDF2-2731-3CF2-A310-543557961180 + 489176 23 QuartzCore 0x00000001a0b3a264 EC26DDF2-2731-3CF2-A310-543557961180 + 488036 24 QuartzCore 0x00000001a0b92edc EC26DDF2-2731-3CF2-A310-543557961180 + 851676 25 QuartzCore 0x00000001a0b10560 EC26DDF2-2731-3CF2-A310-543557961180 + 316768 26 UIKitCore 0x00000001a19a95f0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1791472 27 CoreFoundation 0x000000019f09c218 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 418328 28 CoreFoundation 0x000000019f08a4c0 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 345280 29 CoreFoundation 0x000000019f089b84 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 342916 30 CoreFoundation 0x000000019f089368 CFRunLoopRunSpecific + 572 31 GraphicsServices 0x00000001eb27c1c4 GSEventRunModal + 164 32 UIKitCore 0x00000001a1bd69b0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4073904 33 UIKitCore 0x00000001a1c84d54 UIApplicationMain + 340 34 ***.iOS 0x0000000102fdc5f4 xamarin_UIApplicationMain + 60 35 ***.iOS 0x000000010332f340 do_icall + 316 36 ***.iOS 0x000000010332dc40 do_icall_wrapper + 348 37 ***.iOS 0x000000010332264c mono_interp_exec_method + 2784 38 ***.iOS 0x0000000103320218 interp_runtime_invoke + 236 39 ***.iOS 0x00000001032eee9c mono_jit_runtime_invoke + 1116 40 ***.iOS 0x0000000103296600 mono_runtime_invoke_checked + 148 41 ***.iOS 0x000000010329c8fc mono_runtime_exec_main_checked + 116 42 ***.iOS 0x00000001032f449c mono_jit_exec + 356 43 ***.iOS 0x0000000103008ffc xamarin_main + 2336 44 ***.iOS 0x00000001033e7874 main + 64 45 dyld 0x00000001c52c4734 94AF19E0-4F2A-332F-A08C-04B9B7CB6FAC + 210740 (ObjCRuntime.ObjCException) at ObjCRuntime.Runtime.ThrowException(IntPtr gchandle) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/ObjCRuntime/Runtime.cs:line 2594 at UIKit.UIApplication.UIApplicationMain(Int32 argc, String[] argv, IntPtr principalClassName, IntPtr delegateClassName) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 60 at UIKit.UIApplication.Main(String[] args, Type principalClass, Type delegateClass) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 94 at ***.iOS.Application.Main(String[] args) in /Users/***/***/***/sources/iOS/Main.cs:line 7 Question for the administrators: Can you remove my previous post from July 16?

I installed the IOS 18 beta a day ago. And right away anytime I try to respond to a text message. The app would shut down sometimes it would send the message most times it would just disappear and then if I try to read long messages, it shuts down too.

App / Universal Linking works fine on the "normal" web browser (applies to chrome and safari) however once the page is accessed via "incognito/private" modes app / universal linking redirects the user to the app store instead of the installed application. TLDR: App / Universal Linking doesn't work properly on "Incognito" Mode

Throughout the IOS 18 update feature, my iPhone has been working extraordinary well and there seems to be no issues with the update for the latest gen iPhones/apple products. The only issue I’ve experienced these few months include the torch feature. after the IOS 18 Beta Version 3 dropped, my iPhone seems to have problems when it comes to turning the torch on. It mostly bugs out, like when i turn the torch on, it turns on for a split second and immediatly turns off again. It seems as though now my IPhone 14 Pro Max is unable to run the torch feature. Even after the Version 4 of Beta IOS 18, my iPhone is still unable to run the flashlight and it does the same thing since the last version for now.

4 days after installing iOS 18 beta 3 my iPhone no longer had macro control, .5 zoom, and other features for the Pro models, I’ve tried restarting my phone but nothing changed, settings Keeps saying that the Phone has an unknown part on the camera or it’s not genuine, I bought it brand new on T-mobile last year, I need help wether this is just a beta issue or an actual physical damage