How do you get previews working in a swift package? This talk shows this working, however the following steps do not work. Using Xcode 12 create a new Swift Package Add a simple view with a preview to that swift package (See code below) Attempt to run the preview. See errors Code: #if os(iOS) import SwiftUI @available(iOS 14.0, *) public struct TestView: View { public init() { } public var body: some View { Text(Hello World) } } @available(iOS 14.0, *) struct NoDataView_Previews: PreviewProvider { static var previews: some View { TestView() } } #endif Error: Build input file cannot be found:...TestPackagePreview.o' (in targ SchemeBuildError: Failed to build the scheme TestPackagePreview Build input file cannot be found: ...TestPackagePreview.o' (in target 'TestPackagePreviewTests' from project 'TestPackagePreview' Link TestPackagePreviewTests (x86_64): error: Build input file cannot be found: ...TestPackagePreview.o' (in target 'TestPackagePreviewTests' from project 'TestPackagePrev
Search results for
missing package product
51,072 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
It's incredibly easy to miss, I searched for almost an hour a few months back.Go to https://icloud.developer.apple.com/ and log in. Then, select your container on the left side. Afterwards, click on the small cogwheel in the development area (not production!). In this menu you'll find the option to Deploy Schema to Production….
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
HiI'v produced .app (using UnrealEngine4) and now I want to publish it on Mac AppStore.(UnrealEngine4 has it's own building system, so the app is'nt produced from xcode)Long story short I'v created & installed all certificates that I need, created AppID (say it's com.mycompany.myapp)in Info.plist there is entry:<key>CFBundleIdentifier</key><string>com.mycompany.myapp</string>Now I'm signing the executable:codesign -f -v -s 3rd Party Mac Developer Application: mycompany... --entitlements myapp.entitlements myapp.app/Contents/MacOS/MyAppThe executable get's signed succesfully (I'v also signed all the .dylib that are part of the application and reside there, also succesfully)now I'm signing the whole bundle:codesign -f -v -s 3rd Party Mac Developer Application: mycompany... --entitlements myapp.entitlements myapp.appthis also ends with successnow time to build package:productbuild --sign 3rd Party Mac Developer Application: mycompany... --component myapp.app /Applications --product
Dear support team, is it possible to rename a notarized ZIP package and not to loose the notarized status? One of our ZIP package contains resources and binaries which are code signed. The archive itself is accepted after submitting and uploading during the notarization process (online notarization). Unfortunately, the ZIP cannot be stapled (offline verification). So, is the filename part of the notarized ZIP package or can a ZIP package be renamed? Best regards, Stefan
I am getting an error message (mixed language) while adding the Swift package dependency. Source code mostly contains Swift language and a little bit of Objective-C. Can't we mix Swift and Objective-C language? If so, what is the workaround
Might also be worth noting that these aren't being natively built in xcode, but rather cross compiled via golang's compiler on a linux machine My experience is that Go binaries often have problems with code signing, primarily, because Go does not use the Apple linker [1]. We sign them and notarize (but can't staple because they aren't apps). Understood. But you can and should staple the installer package. My advice here is that you sign all your binaries, from the inside out, and then bundle them up into an installer package, sign that, notarise the installer package, and then finally staple that package. The resulting ticket will cover the installer package and all the binaries it contains. It will be ingested by the system at install time, so it’ll be available when the user goes to run one of your executables. For more details on each step, see Signing a Mac Product For Distribution. For advice on how to test this stuff, see Testing a Notarised Product
Topic:
Code Signing
SubTopic:
General
Tags:
So I've added swift-format as one of my dependencies to my own swift package so that I can use their lint swift package plugin. Here is my Package.swift: // swift-tools-version: 5.7 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: EssentialFeed, platforms: [ .iOS(.v16), .macOS(.v13), .macCatalyst(.v16), .tvOS(.v16), .watchOS(.v9) ], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: EssentialFeed, targets: [EssentialFeed]), .library( name: EssentialFeedTestHelpers, targets: [EssentialFeedTestHelpers]), ], dependencies: [ .package(url: https://github.com/apple/swift-format, .upToNextMajor(from: 0.50700.1)), ], targets: [ // Targets are the basic building blocks of a package. A target can define a module or a test suite. // Tar
Lemme take a step back here. ES products typically ship in one of two ways: If they’re consumer focused, they use an ES system extension. If they’re enterprise focused, they use an ES daemon. It sounds like you fall into the latter category. If so, why are you adopting SMAppService? That mechanism is intended for folks shipping consumer focused products. For an ES client that’s targeting enterprise environments it makes sense to stick with an installer package. In short, SMAppService is meant to be a replacement for things like SMJobBless and SMLoginItemSetEnabled, not a replacement for installer packages and launchctl. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
let package = Package( name: MyLibrary, platforms: [.iOS(.v17)], There is no ios26 option. How do I build it under ios26? thanks
I have a package installer for my .app created with a sequence of commands (pkgbuild, productbuild, xcrun notarytool, xcrun stapler). When this installer is run on a pristine machine, the user is prompted to install Rosetta first before being able to run the installer. Is this expected behavior? Or am I creating the .pkg incorrectly?
Hello everyone, I'm encountering an issue while trying to publish an app on TestFlight. The app in question is Home Assistant, which I've compiled from the source. I am able to compile and install the app on my device without any problems. My company's developer account is properly configured, and I have set Xcode to automatically manage the provisioning profile. The archive is also created successfully, but when I attempt to upload it to Apple Store Connect for testing via TestFlight, I receive the following error: ERROR: [ContentDelivery.Uploader] Asset validation failed (90525) Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: ceac6dcc-9c76-412e-8ea7-f2d2845f8013) I've made several attempts to resolve this issue to no avail. For instance, if I add the missing capability manually, then I am informed that the provisioning profile is incorrect. Howeve
I'm working on an iOS project that uses Swift Package Manager to download and link a private package to it. The package is developed internally in our company, and it contains over 4000 files. The package creates namespaces using extensions, eg: /* Core.swift */ public enum Core { public enum Blobs { } t/* More enum declarations here */ } /* SomeBlob.swift */ public extension Core.Blobs { public class SomeBlob { /* implementation here */ } } The issue that we're facing is that we are unable to access all the classes, structs and enums from the Package, even though they've all been declared public. We are only able to access approximately a quarter of the files (up to the ones beginning with the letter C). Has anyone had this issue before ? Any suggestions are welcome. Thanks in advance :)
We've started having issues a few days ago with StoreKit returning us a list of InvalidProducts when using the sandbox.I've gone through the classic list with no luck...http://blog.gamedonia.com/solve-invalid-product-ids#12We haven't touched that code at all for months, and even when deploying my latest working release build, it returns a list of invalid product ids.Any ideas?Anyone else with the same issue?
Hi Everyone,I'm not sure if i'm in the right section here.. 🙂I'm looking for a method to create a Package installer/downloader.Let me explain it.I would like to create a package installer where people will have choice to tick/untick the software that they want to download or not. (If it's possible in package installer)I have already try this software :- Platypus- Iceberg- Packagesbut i can't find the option to add option to download a file from url.I think of creating a basic package installer which load an automator script to download specific files but didn't succeed.Thanks a lot for your help to everyoneMichael
Hello Apple community ! I'm facing an issue regarding xcstrings in a local package in my project. It's an iOS application with a local package containing multiple targets. The Localizable.xcstrings is located in the app target and contains keys for the app and targets of the local package (Views in the targets look for keys in the main bundle) My issue is that auto detection/extraction seems to work only for keys used inside the app bundle. It doesn't look in the package. However, if I add a Localizable.xcstrings inside a package target, it gets populated. Is this normal behaviour & is there any way to make extraction put the keys in the main bundle xcstrings instead ? I feel like it should be normal behaviour if no xcstrings is found in the package My fallback would be to set all keys in manual extraction state but it's not ideal ;) Thanks in advance for the great work Eric