build disappears

I tried to create a new IOS provisioning profile and re-apply it to the app using Xcode to build it, but I got into trouble. The build is good, but it bounces when running the app. I would appreciate it if you could let me know what to do.

Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (sma

Hi, I’m facing an issue when trying to build a Unity AR project for iOS using Xcode 26.0.1 (Build 17A400) on macOS Tahoe. The build always fails with the following error: Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5196. Details: Unity versions tested: 6.0.0 (6000.0.57f1), 6.2.5, and 6.3 beta Xcode: 26.0.1 (latest) macOS: Tahoe Even a fresh Unity AR template project fails (no external plugins or modifications) Deleting derived data, reinstalling Xcode, and re-exporting from Unity doesn’t resolve it Notes: Downgrading Xcode is not possible because macOS Tahoe requires the latest version. Android builds work fine; the issue only happens on iOS. Question: Has anyone else encountered this linker assertion in Xcode 26 with Unity builds? Is this a known bug in the new Xcode linker, or is there a recommended workaround until Unity or Apple updates their toolchain? Thanks in advance for any guidance!

Hello, My project fails to build/run on a physical device or archive, due to a persistent provisioning error. Exact Error: Provisioning profile iOS Team Provisioning Profile: com.huiwan.Ohra-Journal doesn't include the BGTaskSchedulerPermittedIdentifiers entitlement. I have already performed extensive troubleshooting, and all local configurations appear to be correct: Capabilities: Background Modes with the Background processing option is enabled in the target's Signing & Capabilities tab. Info.plist: The Permitted background task scheduler identifiers key is present in the target's Info.plist, and it contains the correct task identifier (com.huiwan.ohra-journal.refresh). Entitlements File: The .entitlements file is correctly configured by Xcode. Full Reset: I have tried a complete reset procedure, including deleting ~/Library/Developer/Xcode/DerivedData and ~/Library/MobileDevice/Provisioning Profiles/, restarting Xcode, and letting the automatic signing system regenerate the profile from scratc

Does anyone know how to solve this? Suddenly X-code stopped allowing me to build on my iPhone. Works fine in simulato. Failed to install embedded profile for[…] (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).) Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: This app cannot be installed because its integrity could not be verified. Domain: MIInstallerErrorDomain Code: 13 User Info: { FunctionName = -[MIInstallableBundle _installEmbeddedProfilesWithError:]; LegacyErrorString = ApplicationVerificationFailed; LibMISErrorNumber = -402620390; SourceFileLine = 322;

I have created a build tool plugin in one of my SPM packages, and am trying to get it working in my project. It works fine when I build from Xcode, or have at least built the project in Xcode once before with the plugin. But if I try to build the project using xcodebuild on a machine where I have never built the project before, it fails with this error: error: '2.3.0': Invalid manifest (compiled with: [/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc, -vfsoverlay, /var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/TemporaryDirectory.BWwJWG/vfs.yaml, -L, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/ManifestAPI, -lPackageDescription, -Xlinker, -rpath, -Xlinker, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/ManifestAPI, -target, arm64-apple-macosx14.0, -sdk, /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/Mac

I recently started having an issue with my TestFlight builds. In the past, if I built/distributed an app for TestFlight, the AppConnect group automatically received the builds and were able to install the on their devices. When I look in AppConnect, I can see the AC (AppConnect) group shown as a tester and that group shows the users I am expecting in them. The users are receiving an email from TestFlight saying the build is ready. However, when we go into TestFlight, it doesn't show the update being available for that new build. What I have done as a work-around is added my AppConnect users to separate group and add them as testers each time I release a build to TestFlight. Has anyone seen this or can they point out why this may be happening?

Hello, I’m building a health-related app for both watchOS and iOS, which needs to monitor certain health data (e.g., heart rate, active energy). Before updating to watchOS 26, the queries worked reliably without any issues. However, after adapting to watchOS 26, some users have reported that health data updates stop being delivered. What I’ve observed: HKObserverQuery with enableBackgroundDelivery is set up normally. On WatchOS 26, the query sometimes stops delivering updates entirely after a certain point, and once an update is missed, it may stop delivering further updates completely. Restarting the Apple Watch temporarily restores delivery, but the problem reoccurs after some time. This makes background health data monitoring unreliable for my app. Here’s a simplified version of the code we are using: guard let heartType = HKObjectType.quantityType(forIdentifier: .heartRate) else { return } let query = HKObserverQuery(sampleType: heartType, predicate: nil) { query, completionHandler, error in if l

Hello, In my App.xcdatamodeld I have an entity called File. When I am building the project with Xcode, file FileEntity+CoreDataProperties.swift is generated. After upgrading Xcode to version 26.0 (17A324), I am getting the warning: Public import of 'CoreData' was not used in public declarations or inlinable code Any idea how to get rid of this warning since it's a generated file and I can't see any option to change it?