Actually, I found the Obj-C docs for UISliderTrackConfiguration. Below is some sample code. This makes it easy for users to choose one of three positions on the slider. However, I have not been able to get any of my tick mark graphics to actually appear on the slider UI (either I or the beta API must be doing something wrong). UISliderTick *theSliderTick0 = [UISliderTick tickWithPosition:0.0 title:@"-4" image:[UIImage systemImageNamed:@"dot.crosshair"]]; UISliderTick *theSliderTick1 = [UISliderTick tickWithPosition:0.5 title:@"0" image:[UIImage systemImageNamed:@"dot.crosshair"]]; UISliderTick *theSliderTick2 = [UISliderTick tickWithPosition:1.0 title:@"4" image:[UIImage systemImageNamed:@"dot.crosshair"]]; UISliderTrackConfiguration *theConfig = [UISliderTrackConfiguration configurationWithTicks:@[theSliderTick0, theSliderTick1, theSliderTick2]]; theConfig.allowsTickValuesOnly = NO; theConfig.minimumEnabledValue = -4.0; theConfig.neutralValue = 0.0; theConfig.maximumEnabledValue = 4.0; mySlider.trackConfiguration = theConfig;

Anybody have any idea how to use the UISliderTrackConfiguration API from Objective-C? The docs are all for Swift.

Ditto. Submitted FB18845125.

Also experiencing the same issue. Submitted FB18845125.

I'm experiencing all the above issues with beta 4. And now a new issue where segment text/images are not properly aligned vertically. Here's an example...

I experienced this error message too, and was able to resolve it by using TimeMachine to restore my app's Xcode project file to a version from yesterday. The provisioning profile issue started today after Xcode 26b3 offered to update my app's project file, and I approved the updates. That update process altered something with the project's provisioning profile data which Xcode 16.4 did not like or did not understand. The result: Xcode 16.4 was unable to install my app on any of my devices (iPad, iPhone, Mac)-- even though Xcode 26b3 was able to. Prior to making this discovery, I tried most of the troubleshooting tips that you attempted, and none of them worked for me either. It was only after I realized that Xcode 16.4 was able to install my other apps onto my devices, that it dawned on me this issue was confined to a single project. That's when I decided to try restoring the project file from a backup (not the source code; just the Xcode project file).

I experienced this error message too, and was able to resolve it by using TimeMachine to restore my app's Xcode project file to a version from yesterday. The provisioning profile issue started today after Xcode 26b3 offered to update my app's project file, and I approved the updates. That update process altered something with the project's provisioning profile data which Xcode 16.4 did not like or did not understand. The result: Xcode 16.4 was unable to install my app on any of my devices (iPad, iPhone, Mac)-- even though Xcode 26b3 was able to.

I experienced this issue too, and was able to resolve it by using TimeMachine to restore my app's Xcode project file to a version from yesterday. The provisioning profile issue started today after Xcode 26b3 offered to update my app's project file, and I approved the updates. That update process altered something with the project's provisioning profile data which Xcode 16.4 did not like or did not understand. The result: Xcode 16.4 was unable to install my app on any of my devices (iPad, iPhone, Mac)-- even though Xcode 26b3 was able to. The error message I encountered was very similar to what @lydiamatu (the OP) quoted. I realize that this message is an old thread, but thought I'd post this reply in case anybody else working with Xcode 26 beta encountered the same issue and was searching the forums for "provisioning".

Update: I was finally able to fix this issue by changing the project's Build Settings > Apple Clang Language C++ > C++ Language Dialect to "GNU++23" (from "Compiler Default").

Update: I was finally able to fix this issue by changing the project's Build Settings > Apple Clang Language C++ > C++ Language Dialect to "GNU++23" (from "Compiler Default").

Meanwhile, I found a solution to run Xcode 15 on Sequoia.

Meanwhile, I found a solution to run Xcode 15 on Sequoia.

Worked for me as well with Sequoia RC (2024-09-16). Thanks so much, AravShakya! Now I can build my app again (while waiting for showstopper fixes to Xcode 16).

Did you ever get this resolved? I'm experiencing the same fatal compile error with iOS 18 RC and Xcode 16 RC: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here I don't know how to resolve this since the issue involves the is_integral.h file which is part of the Foundation include. This appears to be an Xcode 16 bug as my app builds without errors using Xcode 15.4 (on a Mac running Sonoma instead of Sequoia).

I'm experiencing the same fatal compile error with iOS 18 RC and Xcode 16 RC: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here I don't know how to resolve this since the issue involves the is_integral.h file which is part of the Foundation include. This appears to be an Xcode 16 bug.