I recently installed the Swift OpenAPI Generator on my Xcode project. I used it for a little bit but then decided that it would not work how I wanted it to, so I uninstalled it. I uninstalled all the packages related to the OpenAPI generator, and removed the generator from my projects build phases. However, when I try to build and run my project now, I get an error saying that my application could not find the OpenAPI generator script. I did delete this script, but I also removed it as a run build tool plug-in, so it should not be trying to execute in the first place. I used the instructions found in this WWDC23 video (at around the 9:00 minute mark). I am wondering how to completely remove this plug-in. I have tried searching my XCOde project, but I cannot find any indication of this plug-in still existing within my project. I have tried cleaning the build folder as well, but to no avail. What can I do to resolve this issue?
missing package product
42,955 results found
Post
Replies
Boosts
Views
Activity
I try to use the new VNCalculateImageAestheticsScoresRequest API. Code is compiling and running but delivers the same result for every image Xcode 16 Beta 2 Simulator Did I missing anything ?
I solved it and I'm saying the solution just so it actually shows up on search results. In the Simulator, go under Device -> Erase all Content and Settings. This resets the Simulator's OS. Without building anything to simulate yet, open the Messages app and some random menu will pop up, click OK then quit Messages. In Xcode go to Product -> Scheme -> New Scheme and don't change anything and hit OK. Hit the play button and it'll just work. I tested this on the iOS 15 - iOS 17 simulators and it works despite iOS 15 and 16 giving slightly different errors from iOS 17. Credit: https://forums.developer.apple.com/forums/thread/757781 This solution didn't work for me without resetting iOS on the simulator.
Xcode says 'App' is only available in macOS 11.0 or newer when building an app with a package dependency. As soon as I remove the package, the errors disappear. I anyway set the minimum OS requirements as macOS 14.0+, so how does this error exist?
What about the package itself. Are the minimum deployment you show (macOS 14.0) for this package ? Is it a package you developed or one you imported ?
To answer your direct question… well… I think something might have been lost in translation but it sounds like you’re concerned about the App Review impact of disabling ATS. If so, we can’t really help you here because App Review has the final say as to what is or isn’t allowed on the App Store. However, you can find some info about this in the our documentation. Still, my advice is that you do what endecotp suggested and enable HTTPS on your server. It’s the best option for your users, it makes your app simpler and more secure, it avoids any potential problems with App Review, and with Let’s Encrypt it’s free. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
My App needs to send and receive messages to the server, but my server does not have SSL, so I can only disable ATS in the development stage. But if I want to put the app on the shelf, then I still disable ATS when I put it on the shelf, and the server still does not have SSL. Will it be packaged? Is pp warned and terminated by Xcode? Will it be rejected by the Apple audit department? Can it be put on the App Store normally and provided to all users? Note: My server is completely safe without any security risks. I didn't apply for SSL just because I didn't have enough funds.
VPN products on iOS use the Network Extension framework. They can either: Use Personal VPN to configure the built-in VPN transports. Or create a custom VPN transport, typically as a Packet tunnel provider. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Are you testing this an a ‘clean’ machine? If not, please try that and let me know what you see. I often see problems like this when folks test their final product on their development machine. It’s best to test on a separate machine, one that’s never seen your software before. I usually run tests like this using a VM, restoring the machine from a ‘clean’ snapshot between each test. For an example of that process, see my Testing a Notarised Product. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
It would help if you used redacted App IDs rather that product names. It’s hard for me to understand the mapping between the two. Which App ID is causing your problems? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
The new version of Xcode 15.3 broke the behavior of incrementing build numbers with agvtool which I used to automate to update the build number after each build. The observation is that after running this in my project directory: agvtool bump Xcode removed the section Package Dependencies in the project navigation pane which results in failing a subsequent build with this error message: Missing package product 'mypackage' To solve this I have to reset package caches under File>Packages. This will restore the Package Dependencies section in the navigation pane of Xcode. It seems to be a bug of the new Xcode version 15.3 as this was working without any issues in the previous versions. Any idea?
No, I'm not asking for tax advice here.What I would like ot know is...how are most people handing the requirement in the Section 2, Exhibit B, number 2 ? At the time of this writing it reads:2. Apple shall not collect and remit the taxes described in Section 3.2 of this Schedule 2 for sales of the Licensed Applications to End-Users located in the countries listed below, as updated from time to time via the App Store Connect site. You shall be solely responsible for the collection and remittance of such taxes as may be required by local law....I am a tiny company. I assume that if Apple found it not worth their effort to figure out that tax requirements in that long list of countries, it is not something that any of us would want to try to handle either?Am I missing something? So mostly everyone is just not selling in those countries? (Sadly, a couple of my Beta testers were in one of these countries and I fear that I must now abandon them.)
When a package is published via MDM using the Install Enterprise app command provided by Apple On one of the devices, this command is failing with com.apple.appstored.xpc exception but works fine on other macOS devices having the same restrictions and OS version. We tried restarting the device and also the appstored process via Activity Monitor but it was in vain. I am attaching system logs that contain the exception and stack trace when the command failed. ExceptionLogs
This is the worse service, Developer support do not respond its been 2 months and I cant even put the app live and am losing a lot of business, I can’t go live with this problem. We have been trying to change this account type from individual to business. This is frustrating, What kind of support that do not respond to their customers, Android fixed this long time, I can’t go live with this , I am even struggling to get the DNS number. What does one has to do here to get help, Honestly . So disappointed on apple support Sindi
I have a macOS app which contains a dext. I'd like to distribute it to external testers using TestFlight, so it has to pass Mac App Store review. It failed, because the App Sandbox entitlement was missing. I checked the app, it has the entitlement, but the dext does not. However, the .entitlements file used by the dext does contain App Sandbox set to true. I tried adding a fake-entitlement value to the .entitlements file, and that made it into the dext's code signature, but the App Sandbox entitlement appears to be stripped out by the build process? For a dext target, it isn't possible to add the App Sandbox capability in Xcode's Signing and Capability section. I have to add the entitlement manually in the .entitlement file (or it was put there by the Xcode driver template, I don't remember). I've tried clean building several times, I've tried Xcode 15.0.1, 15.2 and 15.3, but the result is always the same. I'm inspecting the entitlements using codesign -dvvv --entitlements - Does anyone know what I c