Search results for

missing package product

51,068 results found

Post

Replies

Boosts

Views

Activity

Reply to Check whether app is built in debug or release mode
Thanks @DTS Engineer for the detailed snippet. The usage of get-task-allow entitlement gave me idea for updating my previous parsing entitlement approach and I came up with this: struct MobileProvision: Codable { static let current: MobileProvision = { let profileExtension = mobileprovision guard let profilePath = Bundle.main.path(forResource: embedded, ofType: profileExtension), let profileString = try? String(contentsOfFile: profilePath, encoding: .isoLatin1), case let scanner = Scanner(string: profileString), scanner.scanUpToString(), let plist = extractedPlist.appending().data(using: .isoLatin1) else { return .simulatorDefault() } let decoder = PropertyListDecoder() do { return try decoder.decode(MobileProvision.self, from: plist) } catch { return .simulatorDefault() } }() static func simulatorDefault() -> Self { return Self(entitlements: Entitlements(isDebuggable: true, apsEnvironment: .development)) } let entitlements: Entitlements enum CodingKeys: String, CodingKey { case entitlements = Entitlements
Topic: Developer Tools & Services SubTopic: General Tags:
3w
Weird crash: missing symbol Swift.AsyncIteratorProtocol.next()
I got several reports about our TestFlight app crashing unconditionally on 2 devices (iOS 18.1 and iOS 18.3.1) on app start with the following reason: Termination Reason: DYLD 4 Symbol missing Symbol not found: _$sScIsE4next7ElementQzSgyYa7FailureQzYKF (terminated at launch; ignore backtrace) The symbol in question demangles to (extension in Swift):Swift.AsyncIteratorProtocol.next() async throws(A.Failure) -> A.Element? Our deploy target is iOS 18.0, this symbol was introduced in Swift 6.0, we're using latest Xcode 16 now - everything should be working, but for some reason aren't. Since this symbol is quite rarely used directly, I was able to pinpoint the exact place in code related to it. Few days ago I added the following code to our app library (details omitted): public struct AsyncRecoveringStream: AsyncSequence { ... public struct AsyncIterator: AsyncIteratorProtocol { ... public mutating func next(isolation actor: isolated (any Actor)? = #isolation) async throws(Failure) -> Element? { ...
Topic: App & System Services SubTopic: Core OS Tags:
3
0
219
3w
Static library produced by Xcode 26 causes link error on Xcode 16
When a static library is built with Xcode 26 (with deployment target set to iOS 13) and then linked into an app project compiled with Xcode 16, the build process fails with the following linker error: Undefined symbols for architecture arm64: _swift_coroFrameAlloc This occurs even though both the static library and the app project have their deployment targets set to iOS 13.0. The static library works on Xcode 26, but fails to link on Xcode 16. This issue shows up with certain Swift syntax. For example, in my case, using a property getter and setter caused the compiler to emit a reference to _swift_coroFrameAlloc, which in turn triggered the issue. This issue prevents us from distributing pre-built static libraries compiled with Xcode 26 to teammates who are still using Xcode 16. I’ve filed feedback for this issue (FB21130604). Is there any way to work around it? For example, by adding specific Build Settings or something similar? A demo project is available here: https://github.com/Naituw/SwiftLibraryDeploym
Topic: Developer Tools & Services SubTopic: General Tags:
2
0
256
3w
Severe Delay When Tapping TextField/Searchable on iOS 18 (Real Device) — XPC “Reporter Disconnected” Loop Until Keyboard Appears
I’m running Xcode 26.1.1 (17B100) with deployment target iOS 18.0+, and I’m seeing a consistent and reproducible issue on real devices (iPhone 13 Pro, iPhone 15 Pro): Problem The first time the user taps into a TextField or a SwiftUI .searchable field after app launch, the app freezes for 30–45 seconds before the keyboard appears. During the freeze, the device console floods with: XPC connection interrupted Reporter disconnected. { function=sendMessage, reporterID=XXXXXXXXXXXX } -[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID. inputModality = Keyboard customInfoType = UIEmojiSearchOperations After the keyboard finally appears once, the issue never happens again until the app is force-quit. This occurs on device Reproduction Steps Minimal reproducible setup: Create a new SwiftUI app. Add a single TextField or .searchable modifier. Install Firebase (Firestore or Analytics is enough). Build and run on device. Tap the text field immedi
Topic: UI Frameworks SubTopic: SwiftUI
1
0
91
3w
Reply to findNavigator
Thanks for your question, looks like you ask the same question last week at https://developer.apple.com/forums/thread/807276 Trying to see what you asking but I am a little lost. I would recommend to provide more information about what you are trying to accomplish if you can. Here are a few suggestions that might help it attract more attention: Provide more details: Expanding on your post to include any error messages, code snippets, steps you've already taken to troubleshoot, and the expected/actual outcomes would be very helpful. Be specific about your technology stack: Clearly state the programming languages, frameworks, or tools you are using. Check for duplicates: Before posting, make sure your question hasn't been asked before. You can use the search bar to find similar threads. I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.
Topic: Graphics & Games SubTopic: General
3w
Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
Hi everyone, I’m trying to register fonts system-wide using CTFontManagerRegisterFontURLs with the .persistent scope. The fonts are delivered through Apple-Hosted Background Assets (since On-Demand Resources are deprecated). Process-level registration works perfectly, but persistent registration triggers a system “Install Fonts” prompt, and tapping Install causes the app to crash immediately. I’m wondering if anyone has successfully used Apple-Hosted Background Assets to provide persistent, system-wide installable fonts, or if this is a current OS limitation/bug. What I Expect Fonts delivered through Apple-Hosted Background Assets should be eligible for system-wide installation Tap “Install” should install fonts into Settings → Fonts just like app-bundled or ODR fonts App should not crash Why This Matters According to: WWDC 2019: Font Management and Text Scaling Developers can build font provider apps that install fonts system-wide, using bundled or On-Demand Resources. WWDC 2025: Discover Apple-Hosted Backgr
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
3
0
180
3w
Provisioning Profile Not Including Push Notifications Capability
Provisioning profiles created for my App ID are not including the Push Notifications capability, even though Push Notifications is enabled in the App ID configuration in Apple Developer Portal. I have enabled Push Notifications for my App ID (com.abc.app) in the Apple Developer Portal. The capability shows as enabled and saved. However, when provisioning profiles are generated (either manually or through third-party tools like Expo Application Services), they do not include: The Push Notifications capability The aps-environment entitlement This results in build failures with the following errors: Provisioning profile *[expo] com.abc.app AppStore [timestamp] doesn't support the Push Notifications capability. Provisioning profile *[expo] com.abc.app AppStore [timestamp] doesn't include the aps-environment entitlement. Steps Taken ✅ Enabled Push Notifications in App ID configuration (com.mirova.app) ✅ Saved the App ID configuration multiple times ✅ Waited for Apple's systems to sync (waited 5-10 minutes) ✅ Remov
Topic: App & System Services SubTopic: Notifications Tags:
1
0
91
3w
Reply to Can I use apple.logo placed on the top of apple sign in related view?
Guideline 5.2.5 Apple Products: states: Don’t create an app that appears confusingly similar to an existing Apple product, interface (e.g. Finder), app (such as the App Store, iTunes Store, or Messages) or advertising theme. Apps and extensions, including third-party keyboards and Sticker packs, may not include Apple emoji. Even more precisely, in Guidelines for Using Apple Trademarks and Copyrights (https://www.apple.com/fr/legal/intellectual-property/guidelinesfor3rdparties.html): Use of the keyboard Apple Logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement 2. Apple Logo and Apple-owned Graphic Symbols: You may not use the Apple Logo or any other Apple-owned graphic symbol, logo, or icon on or in connection with web sites, products, packaging, manuals, promotional/advertising materials, or for any other purpose except pursuant to an express written trademark license from Apple, such as a reseller a
Topic: Design SubTopic: General Tags:
3w
Reply to Mac App Packaging
Inno Setup was a sweet app. I used to use that when I made Windows software. I don't know anything about Filemaker. A quick search says that runtimes were deprecated and removed years ago. Apparently Filemaker 18 was the last version to support them. There is some kind of iOS App SDK that may still be supported. It doesn't sound like this would be a quick and/or easy solution, but that seems to be all there is. After Hypercard, there was never the same kind of custom database app community (Clipper, Access, Paradox, etc.) as on PCs. I don't know what you mean by inherited icons. A DMG is just a disk image. Its use in installing software is problematic. Why use a zip files or pkg installer when you can use DMGs that make it 3 times more difficult? Look at the pkgutil tool. All you need is a folder with the app you want to install. Create a directory tree of all the locations where you want to install files. Then use pkgutil to create an installer for that. Forget everything I said about the Mac App St
Topic: Code Signing SubTopic: Notarization
4w
Reply to Mac App Packaging
Etresoft, thanks for the reply. I assure you, I'm not trying to make work for myself or others, merely attempting to package a Filemaker 18 Runtime app. A Windows bod, I had no trouble creating a signed exe using Inno Setup, but have been pulling teeth trying to do the equivalent for the Mac version. I began by reading the official Mac guides, but found them impenetrable, so turned to Copilot and Chatgpt. After many weeks of toing and froing, I have reached the stage where I can script create a DMG, but am currently having trouble with inherited icons. Are you saying that if I had merely uploaded my runtime to the Mac App Store, I might have avoided all of this?
Topic: Code Signing SubTopic: Notarization
4w
Can an iOS app programmatically detect if it's built for release or debug?
Is it possible for an iOS app to programmatically detect if its built for TestFlight/App Store distribution versus built for development? The motivation for doing this is so that the app can detect if a push server should send pushes using the Apple production server or the sandbox server - when the app sends the push token to the server, I'd like it to additionally send an indicator to the server so the server knows which of the Apple servers to use. Is there a way to achieve this? TIA
Topic: App & System Services SubTopic: Core OS Tags:
6
0
369
4w
Reply to Check whether app is built in debug or release mode
Earlier I wrote: But, honestly, it sounds like a fun weekend project And indeed it was (-: Pasted below is some iOS code that is able to detect how your code is signed using only public APIs. To do this, it uses a sneaky combination of XPC loopback and XPC peer requirement checking. This code comes with a bunch of caveats. Read the doc comment before you use it [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] By my count the doc comments represent well over half the total number of lines (-: import Foundation extension CheckSelfEntitlement { /// Checks whether the current process claims the get-task-allow /// entitlement. /// /// - warning: As explained below, you shouldn’t use this routine but /// instead should use ``isGetTaskAllowTrue()``. This routine exists solely /// to illustrate the following point. /// /// This routine checks for the presence of the entitlement, rather than /// checking for it being present with a particular
Topic: Developer Tools & Services SubTopic: General Tags:
4w
Reply to Mac App Packaging
I'm afraid you'll have to provide a bit more context. Do you have a specific question that someone could answer? Are you talking about building or installing? For building, the standard process is simple. Xcode > Product > Archive. There is no step two. For distribution, you can choose the Mac App Store or direct distribution. If you choose the Mac App Store, you're done with the installer package at that point. For direct distribution, you'll still need to zip the resulting app. You can do that in the Finder with control-click or double-click and choose Compress. Of course, if you're more of a masochist, there are many, many suggestions from the internet on how to make the process more difficult. You're correct that those procedures can get Kafkaesque in no time. But you don't have to do it that way if you don't want. And if you don't like those procedures, then I don't see the point of attempting them.
Topic: Code Signing SubTopic: Notarization
4w
Xcode won't run my app; it runs fine from Finder.
I'm developing in Objective C with Xcode on a Mac exclusively to run on Mac and all of a sudden when I try to run I get the message: a build only device cannot be used to run this target. If I go to the destination folder, the newly built app is there and runs from Finder, I just can't get it to run from within Xcode, which is inconvenient for testing. What setting am I missing or has changed? Up to now I could build and run with no problem.
Topic: Developer Tools & Services SubTopic: Xcode
1
0
77
4w