When looking at code in documentation, registration is done differently, by creating a default content configuration and then adjusting: let cellRegistration = UICollectionView.CellRegistration<UICollectionViewListCell, Int> { cell, indexPath, item in var contentConfiguration = cell.defaultContentConfiguration() contentConfiguration.text = "\(item)" contentConfiguration.textProperties.color = .lightGray cell.contentConfiguration = contentConfiguration } Could you also test with a log: let mainCellRegistration = UICollectionView.CellRegistration<EmotionExplorerCell, Item> { cell, indexPath, item in print("cell", cell, indexPath, item) // <<-- ADD THIS switch item { case .main(emotion: let emotion, icon: let iconName, red: let red, green: let green, blue: let blue) : cell.configure(iconName: iconName, title: emotion, red: red, green: green, blue: blue) cell.index = indexPath.row cell.delegate = self case .title(title: -, buttonTitle:

However, calling the cell delegate method from the cell is not calling the method in the view controller. It's not very clear.   calling the cell delegate method from the cell Which method is it ? repromptLLMForIconName ?   is not calling the method in the view controller. Which method is it ? Have you checked that delegate is not nil ? print("delegate", delegate) delegate?.repromptLLMForIconName(iconName, index: index, emotion: emotion, red: red, green: green, blue: blue)

Why would a third party have to know and the right to know ? IMHO that would be a privacy (and possibly security) breach, isn't it ?

Just a personal opinion. Unless you have really imperative reason to refactor your project, and if your app works correctly, I would not undertake such a work. You will spend huge amount of time with the risk to create a lot of bugs. In any case, make sure you have a complete project back up (not only Time Machine).

I cleaned Xcode caches. I reinstalled Xcode 14.2 To no avail. If I try to add simulator, then look at the simulators list, I get a whole bunch of(all for iOS 16.2). But no one appear in the target list for compiling. I'll try solution proposed here: https://stackoverflow.com/questions/78372541/xcode-doesnt-show-simulators Even though XProtectPayloads. If it says 151, it doesn' work. I updated system to the latest available for this MacBook. No change. I disabled xprotect. No change.

In UIKit, you can call override var prefersStatusBarHidden: Bool { return true } In SwiftUI, equivalent by calingl the modifier: struct ContentView: View { var body: some View { Text("Hello, World!") .statusBar(hidden: true) } } More details here: https://medium.com/app-makers/how-to-hide-the-status-bar-in-swiftui-all-methods-explained-07eeca7ac3d6

We all would like all bugs to fixed immediately, at our will. But that does not work like this. iOS 26 is a beta, with all the potential issues. You use it at your own risk But you can: report a bug in feedback assistant use a released version of iOS contact the web site.The problem may be on their side.

That is not a question for this forum, which is about your app development, not about using apps. Don't forget that iOS 26 is beta that you use at your own risks. If you need stability you should stay with a released version. So,you should either: contact TikTok (maybe a users forum) file a bug report

It is indicated in release notes: https://developer.apple.com/documentation/watchos-release-notes/watchos-26-release-notes More details here: https://www.macrumors.com/2025/06/25/watchos-26-hermes-crash-issue/

If your app is doing exactly the same thing than other apps, it will risk a spam refusal. In any case, it is not an argument that other app have been accepted and hence your app should as well. You don't know the exact content of other apps, nor the explanations they may have provided. You have to focus on your app and answers the questions asked. And provide clear and factual answers, not what you think the reviewer should do… Good luck.

Some of my error messages have characters outside the straight ASCII character set (i.e. "å"). The editor correctly displays these, but I get plenty of Illegal Character warnings and the messages do not display properly. Could you show related code, as well as the exact warnings and a screenshot of messages you get. That will help understand what's happening and hopefully propose solution.

Don't wait, contact support before your account expires. And keep track of your submission.

There seems to be some minor improvements with Xcode 26.0 ß2. Notably, during swipe, the segment no more hidden. But when released, its title still hidden by a white front. Not clear whether the issue is in: Xcode simulator iOS 26

@mutou519 have you checked that you saved to userDefaults ? May be, when you quit the app (by swiping up ?), you don't go through the code that saves userDefaults. To check: in the part of code where you intent to save, add a print statement to check in logs that it was effectively done. If that's the case, you should save userDefaults in SceneDelegate: func sceneDidEnterBackground(_ scene: UIScene) { // Save userDefaults } and also possibly here: func sceneDidDisconnect(_ scene: UIScene) { } and read here: func sceneWillEnterForeground(_ scene: UIScene) { // read userDefaults } You could also save in AppDelegate: func applicationWillTerminate(_ application: UIApplication) { // Save userDefaults }

I tested (with segmented control in storyboard) and noticed several issues: if behaviour for both segments is "Enabled" and "non selected" I cannot switch from First to second the title disappears, hidden by a white mask if first segment selected (in storyboard) when selected second, its title is hidden I can slide a first time and everything displays OK I can swipe back to first But title of first is hidden as well If I select first by clicking, cannot swipe anymore… Note: this issue of title hidden when item selected occurs also with tabbar buttons.