I'd like to know the answer to this...

I have a complex project with > 10 targets and also have issues with exporting localizations. Using Xcode 15. All my targets build in both DEBUG and RELEASE mode. It is only when I try to export localizations that it breaks. The error is always cannot find UIKit. Cleaning the project and deleting derivedData folder has not worked for me. It would be ideal if I could do an export localization for a specified target only

I also have the same issue. It appears that after 10 UDIDs, Apple now takes 24-72 hours to update new registered UDIDs. I got my new iPhone 15 yesterday and wanted to switch development to it, but am stuck waiting. As a consulting member of various companies I notice I could add my UDID to the other companies I'm enrolled as a developer with and it would immeditialy be available. But only if I had 9 or less registered devices. I did read somewhere that it's a new rule. See this page: [https://developer.apple.com/help/account/reference/device-registration-updates/). It clearly states: " Enabling registered test devices may require additional processing for new Apple Developer Program memberships or memberships renewed after expiration for one month or more. Although the device is registered during this time, the device identifier won’t be included in provisioning profiles until processing completes. Existing active memberships are not impacted by this change. " So it's a new policy I guess (?)

Exporting localizations is a mess and doesn't work for complex projects with many targets. For one thing targets which build both for RELEASE and DEBUG fail when I look at the report navigator for exporting localizations.

I am also having the same issues, but using Xcode 15 on Sonoma. It's frustrating that the build settings for exporting localization are hidden and can't be accessed. All my targets compile and link both for release and debug. I have over 10 targets and the only way I have been able to fix this issue is by removing targets until *** works, And then adding them back in. But I need to export localizations for all of the targets! Help!!

Ok, so that post install hook doesn't work. I checked my project and target(s) settings and I have Defines Module set to YES for project, all targets and all pods. Unfortunately I don't know what build settings are used when exporting localizations so I can't change it. If I do a release build or a debug build of all my targets it works with no errors, so why doesn't exporting localization work as well? The only way I have been able to get this to work is to make start removing targets until it works and then put them back. There's got to be a better way. Does any one know how to see the build settings used when exporting localizations?

Here's the color from the color catalog. Its name is "MyButtonBackgroundColor". It's a single color, but this issue also happens when the UIColor form the catalog has Any, Dark and Light sub colors (file Contents.json): { "colors" : [ { "color" : { "color-space" : "srgb", "components" : { "alpha" : "1.000", "blue" : "60", "green" : "60", "red" : "60" } }, "idiom" : "universal" } ], "info" : { "author" : "xcode", "version" : 1 } }

Here's the viewContoller: // // ViewController.swift // storyboardTest // // Created by Salvatore Cataudella on 8/16/23. // import UIKit class ViewController: UIViewController { @IBOutlet var triggerForBugButton: UIButton! @IBOutlet weak var buttonTopConstraintInitiallyUnistalledInStoryBoard: NSLayoutConstraint! @IBOutlet weak var buttonCenterConstraintInitiallyInstalledInStoryBoard: NSLayoutConstraint! var initialText: String? = nil var toggle: Bool = false @IBAction func pressMeAction(_ sender: UIButton) { toggle = !toggle if toggle { sender.setTitle("I'm at the top. Press me!", for: .normal) buttonCenterConstraintInitiallyInstalledInStoryBoard.isActive = false buttonTopConstraintInitiallyUnistalledInStoryBoard.isActive = true } else { if let title = initialText { sender.setTitle(title, for: .normal) } buttonTopConstraintInitiallyUnistalledInStoryBoard.isActive = false buttonCenterConstraintInitiallyInstalledInStoryBoard.isActive = true } UIView.animate(withDuration: 0.4) { self.view.layoutIfNeeded() } } override func viewDidLoad() { super.viewDidLoad() // Do any additional setup after loading the view. initialText = triggerForBugButton.title(for: .normal) } }

Here's the test project. The main storyboard:

I've encountered a challenge in replicating the alpha resetting issue within a basic app setup. The particular screen where this issue arises is intricate, and I'm constrained by time to simplify it to the root cause. However, a similar problem is evident with NSLayoutConstraint. In my storyboard, there's a button. Initially, it's vertically centered using the constraint buttonCenterConstraintInitiallyInstalledInStoryBoard. Additionally, there's another constraint, topConstraintInitiallyUnistalledInStoryBoard, which positions the button at the top but is uninstalled by default. On pressing the button, I switch between these constraints, animating the button's movement from the center to the top and vice versa. This works as expected. But, if I activate the initially uninstalled constraint by pressing the button and then either toggle between light and dark modes or rotate the device, the topConstraintInitiallyUnistalledInStoryBoard reverts to its uninstalled state, reactivating the other constraint. Fortunately, this behavior is consistent on both a physical device and an iOS 16.4 simulator. I'm open to sharing the code if there's any interest.

Hello again, I want to clarify my previous post. Despite the export localizations error related to a pod's umbrella.h file, the pod itself builds successfully. The issue seems to be with my application's source files, which can't find this file only during export localizations, despite successful regular builds. Any insight appreciated. Thanks again!

Our app was stuck in review from December 20th to January 5th 2023. Prior submissions were always approved within 48 hours, so we found this disturbing. Went to the Apple Developer Contact Us Page (link in post above this one), and asked for someone to contact us by phone. Within 2 minutes we got a call from Apple and explained that this version has critical updates and were told that an email had been sent to the App Review team to look into this matter. They said to allow 24-48 hours prior to getting a reply. With 5 minutes of that call ending our app was finally approved.

All is good again. it was an app store connect issue that was always generating a false positive for private API usage.

I now have the same issue as soon as I try to go to apps. It's just blank. I was able to finally upload my app via transporter and it was accepted for internal testing. All day long just trying to submit the app was either never making it in, or would be rejected when processing due to the private api usage issue

Great news! I did not get the ITMS-90338 error email and my app was approved for internal testing. Can't submit it for external TestFlight review because my apps page is blank at the moment, so I'll have to wait until tomorrow