Search results | Apple Developer Forums

Reply to Swift Package can be MAKE_MERGEABLE?

This is not a solution. it failed at the build time with error: The package product 'MyPackage' cannot be used as a dependency of this target because it uses unsafe build flags.

Developer Tools & Services Xcode

Dec ’23

Reply to Error while generating a DocC based documentation for a Swift Package

This sounds like it may be a general Swift Package Manager dependency resolution issue. If you see the same error when you try to build from the command-line using: $ swift build --product InternalFramework then I would recommend either opening an issue on the open-source Swift Package Manager repository or filing a Feedback.

Developer Tools & Services Xcode

Jul ’22

Reply to Notarization fails for flat installer package containing notarized app

You’re building your installer package using a third-party tool. Does the problem reproduce if you build it using Apple’s tools? You don’t need to build something production ready here; just use our tools to create a package you can test against the notary service. There’s a simple command for doing that in Packaging Mac Software for Distribution. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Code Signing Notarization

Feb ’23

Reply to EAS build works in Expo Go & Simulator, TestFlight app crashes on open

Solved this one myself, but for anyone experiencing an operator() crash, be sure to read through the react navigation docs, then find exactly which part of react navigation you used (ie. Stack, Drawer, etc) as there can be some additional packages to add to ensure it runs cleanly on TestFlight. My problem was one missing package that needed to be added.

App Store Distribution & Marketing TestFlight

Jul ’22

Reply to ios14 "Notifications are not allowed" ERR

In my case, Build Settings - Packaging - Product Name was not English. Changed to English and worked. It was okay to set the name in other languages in iOS 13 though.

App & System Services Core OS

Sep ’20

Reply to SMJobBless privileged helpers and granting permission

Thanks Quinn, Sorry, yes, my sloppy terminology of The Finder which I often use for unattached dialogs the user sees. I did not know this about the Full Disk Access being different so my experiments with plists for the priviledge helper need to be redone. One of the operations my helper is doing that needs Full Disk Access is downloading a pkg and checking it is signed. None of the normal security api's appear to work with pkg's, maybe I missed something there, I can check apps and so forth on disk. So I end up running /usr/sbin/pkgutil --check-signature instead as I could not figure out how pkgutil is implemented. Did I miss something in the security api, should I be able to look at a pkg's validity?

Privacy & Security General

Apr ’22

Reply to Testflight down

My issue has been solved. A new installed package make the microphone on as default and I have to add NSMicrophoneUsageDescription in my info.plist. Some mails from app store has pointed out the problem but I missed them.

App Store Distribution & Marketing TestFlight

Oct ’24

Reply to Notarizing Dmg with an unsigned element

Our product is a developpement tool that can be simply used as a database.Some customers will sign their customized binaries and some will not.If they do not then the problem is that they will still distribute a damaged signed (with our certificate) package because the signature will be damaged due to customization.We do not want to provide, by design, a means to create product with wrong signature.

Code Signing General

Dec ’19

Reply to Xcode 11 how to work with .crash files?

Not sure how viewing crashes in Xcode is supposed to work either. Wasn't able to find anything useful when clicking Open in Project.For me, a couple of times I noticed vital information was missing when viewing the crash in Xcode (missing method calls on the stack but they were in the .crash log). So I right-clicked on the crash in the list on the left and choose Show in Finder which reveals a package with .xccrashpoint in Finder. I then right clicked that .xccrashpoint package in Finder and choose Show Package Contents and then dug through subfolders until I got to the Log folder with the .crash files in it. Then I just opened the .crash in Console. Reading the .crash in Console was a lot more useful. Was able to determine what caused the app to crash and was able to fix it in an update.

Developer Tools & Services Xcode

Mar ’20

Reply to Swift Package with Resources – Upload issue

OK. It's working fine. What I did not understand was that I needed to change the Info.plist file that was located *inside* the archive. I initially thought it was supposed to be somewhere in the Package. So the process is: Create an archive and select it in Xcode Organizer. Show in Finder. Open package contents. Go down the Folder structure (Products -> Application) until you find your .app file. Again, show package contents. There should be your package .bundle file. Again show package contents. Here you should see the Info.plist file. Open it in Xcode and remove the Executable file entry. Save and return to Xcode Organizer. Now you can Distribute the app.

Developer Tools & Services Xcode

Jul ’20

Swift executables in installer packages (.pkg) preinstall/postinstall

It seems that preinstall/postinstall scripts in installer packages (.pkg) are not limited to shell scripts, but can be any kind of executable (e.g. compiled Swift programs). This sounds like an exciting possibility to re-use logic, constants, tests etc. from the app that is being installed, and at the same time benefit from Swift features like type safety for complex installer scripts. Has anyone done this? What were your experiences? Is it advisable, or is it likely to break on the next OS update?

App & System Services Core OS

2

0

315

Nov ’24

This package is incompatible

This package is incompatible with this version of OS X and may fail to install.Heads up for anyone who makes packages. If you write to SIP protected locations, (even symlinks) you will get this warning.Example:Writing to /var - badWriting to /private/var - goodFrom now on it might be ideal to write to the full path as these are not SIP protected./private/etc/private/tmp/private/var

App & System Services Core OS Beta macOS

0

2.2k

Jun ’15

Reply to App rejected due to... Inappropriate content!

You are missing the reasonable connection between tobacco products and e-cigarettes 1.4.3 Apps that encourage consumption of tobacco products...are not permitted....Apps that encourage minors to consume any of these substances will be rejected.

App Store Distribution & Marketing App Review

Jun ’17

Reply to No such module 'FirebaseFirestore'

Interesting, I am just learning iOS, and during my courses I used Firebase but installed via CocoaPods, this time I added the package via add packages and when I want to use the Firestore DB to add in the app delegate also get this error, wonder what the issue could be. So the authentication features all work, but the Firestore seems to be missing for some reason. Will try and re install it later, but updating the package did not help. I am on Xcode 14.2 (14C18)

Developer Tools & Services Xcode

Apr ’23

Problem with swift package manager caching and binary package

I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife

Developer Tools & Services Xcode Swift Packages

1

0

2.1k

Sep ’22

missing package product

Post

Replies

Boosts

Views

Activity