I have a Unity AR project that I want to build for iOS. The build in Unity succeeds just fine, but when it opens in XCode, whatever I do, it keeps showing this error in GameAssembly: Command PhaseScriptExecution failed with a nonzero exit code. This error also doesn't open when choosing Reveal in Log. I have added the IL2CPP package in the Unity version, deleted and reentered scenes and no issue on Unity's side. On XCode I signed in with my developer account, tried deleting derived data, made a clean build and still the issue persists.
Search results for
missing package product
51,056 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi everyone, I’m experiencing an issue with In-App Purchases during App Review. What works My consumable IAP products load correctly using StoreKit2. TestFlight (sandbox) purchases work perfectly. Localizations are filled in and valid. Paid Apps Agreement, banking, and tax forms are active. IAP products are properly created in App Store Connect and marked as “Developer Action Needed” only because they wait for approval with the new binary. What fails During review I received: “We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, we were not able to complete a purchase.” They didn’t provide any more technical details. Additional context The StoreKit configuration file is not included in the app archive. Product identifiers perfectly match those in App Store Connect. StoreKit2 purchase() works as expected on TestFlight. The app does not use server-side receipt validation - purchases are handled purely throug
Hello everyone, I’m an iOS developer from Türkiye, and I’m currently facing a serious issue regarding my Apple Developer account termination (Appeal Ticket: APL255848). Problem: I have removed all references, icons, descriptions, and metadata related to my previous app name (“Nano Banana”) both inside the app and on the App Store listing. I submitted updated assets, screenshots, and a new metadata package. However, the App Review Board seems to still be seeing old cached metadata, old icons, or previous descriptions that no longer exist in my build. Because of this, every response from App Store Connect repeats the same text, even though I have already made and proven all required changes. Current Situation: My account is terminated, and my appeal has been pending for over 3 weeks with identical non-actionable responses. I am not receiving my revenue for the past 2 months. I want to comply fully with the Apple Developer Program Agreement and provide any documents required (invoices, trademarks, API i
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Hi everyone, I'm currently working on a native macOS app (built with SwiftUI) and I'm trying to implement Password AutoFill functionality so users can use their saved credentials from Keychain or third-party password managers. I've gone through Apple's documentation, WWDC sessions, and sample code, but I've noticed that the resources primarily focus on iOS and web implementations. There's very limited guidance specifically for macOS. I've set up: Associated Domains entitlement with the webcredentials: service The apple-app-site-association file on my server TextField with .textContentType(.username) and SecureField with .textContentType(.password) However, I'm still not seeing the expected AutoFill behavior on macOS like I would on iOS. Has anyone successfully implemented Password AutoFill on a native macOS app? Are there any macOS-specific considerations or additional steps required that differ from iOS? Any guidance, sample code, or pointers to documentation I might have missed would be greatly app
I'm experiencing an issue where monthly and family monthly subscriptions fail immediately with purchase cancelled in TestFlight, while yearly and family yearly subscriptions work correctly. Setup: All 4 products in same subscription group All show Ready to Submit status Using react-native-iap with StoreKit 2 Testing in TestFlight sandbox The Problem: Yearly subscriptions work fine Monthly subscriptions fail immediately with E_USER_CANCELLED (no dialog appears, user didn't cancel) What I've verified: No active subscriptions (getAvailablePurchases() returns empty) No pending transactions Same subscription group for all products Product IDs match App Store Connect Code is identical for all products Error: E_USER_CANCELLED fires immediately when calling requestPurchase() for monthly products, but yearly products proceed normally. Questions: Why would monthly fail while yearly works (same group, same config)? Could this be sandbox state corruption for monthly products
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Subscriptions
StoreKit
In-App Purchase
TestFlight
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. The screenshot above is the iOS system's crash log Just clarify what we’re talking about here, this is an Apple crash report from iOS 26.1: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 … Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 ??? 0x0 ??? 1 Test808813 0x10058c128 -[MainViewController tableView:didSelectRowAtIndexPath:] + 100 2 UIKitCore 0x1a563bc98 -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:isCellMult… 3 UIKitCore 0x1a563bfbc -[UITableView _userSelectRowAtPendingSelectionIndexPath:animatedSelection:] + 255 4 UIKitCore 0x1a563c0c8 -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 215 5 UIKitCore 0x1a407d878 -[_UIAfterCACommitBlock run] + 71 … You’re concern is with that SIGKILL, where prior to iOS 18 this was a SIGSEGV. That doesn’t strike me as a proble
Topic:
App & System Services
SubTopic:
Core OS
Tags:
[quote='868752022, DMSAS, /thread/794045?answerId=868752022#868752022, /profile/DMSAS'] However, some Macs still have issues with malicious software [/quote] My advice is that you test your notarised software on a ‘clean’ machine. I generally use a VM for this. See Testing a Notarised Product. If that test fails, there’s definitely something wrong with your product and you should investigate that. I have lots of advice on that topic in Resolving Trusted Execution Problems. If that test succeeds but you receive sporadic reports of Gatekeeper problems from your users, that’s a trickier issue. It’s possible that you have a Gatekeeper problem with a specific OS release. You can investigate that by re-running the above-mentioned test process with that release. However, it’s more likely that there’s something borked on that user’s machine. That puts you in a bit of a bind: You want to help the user with their problem. But debugging their machine configuration problems isn’t really your core busine
Topic:
Code Signing
SubTopic:
General
Tags:
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
[quote='809584021, st-gab, /thread/809584, /profile/st-gab'] is it possible to rename a notarized ZIP package and not to loose the notarized status? [/quote] Absolutely. I think you might benefit from reading Notarisation Fundamentals, which explains what the notary service actually does. Once you understand that, you should be able to work out for yourself what post-notarisations operations are OK. Specifically, you have watch out for any operation that breaks the seal on a code signature, such as: Modifying a Mach-O image Modifying the contents of a bundle Beyond that, everything else is pretty much fair game. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
should mention we seem to have lost alot of previously uploaded builds in test flight
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
PHPhotoLibrary.authorizationStatus(for: .readWrite) == .authorized Iinfo.plist Privacy - Photo Library Usage Description set I check authorization before attempting to get the photoPickerItem.itemIdentifier, but every time the return value from itemIdentifier is nil. Seems I missing some permissions, but unsure why the system is still keeping _shouldExposeItemIdentifier set to false.
Topic:
Media Technologies
SubTopic:
Photos & Camera
I have this problem on VisionOS. When I dismiss and reopen a window from a ImagePresentationComponent, the window misses the resize ui elements when I look at the window corners. The rest of the window ui elements (drag, close...) are there. Resizing was possible before the window was dismissed. The code is something like this: WindowGroup(id: image-display-window,..... } .windowResizability(.automatic) .windowStyle(.plain) I call dismissWindow() from the window view and it is dismissed correctly. Then I call openWindow(id: image-display-window, value: data) from another view to reopen it. It reopens but it missing the possibility to resize. Anyone knows how to fix this? Thanks.
运营了一年多app,更新了很多版本,这一版更换了下ui的预览图,然后更新的时候一直正在等待审核,等了很多天没有结果,给苹果发了邮件询问,然后被标记封号下架了?请问这个是怎么回事,就是常规更新为什么不审核,然后又下架了?申诉了越没有任何回复邮件,这妥妥的霸王条款, appid:6670458903 串聊 请求苹果公司能开发者给恢复正常更新,谢谢 Pending Termination Notice Upon further review of the activity associated with your Apple Developer Program membership, it's been determined that your membership, or a membership associated with your account, has been used for dishonest or fraudulent activity, in violation of the Apple Developer Program License Agreement. Given the severity of the identified issues, your account has been flagged for removal. Because your account has been flagged for removal, any earnings payments are paused and app transfers are disabled. Creating new accounts after receiving this message may result in the termination of the new or associated accounts. Evidence of Dishonest or Fraudulent Activity App submissions from your account have repeatedly violated the App Review Guidelines in an attempt to evade the review process. After multiple resubmissions, the
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Thank you for your reply. Unfortunately, creating a package using productbuild results in the same zero-byte file written to /Applications. I used the command: productbuild --sign --component /Applications Interestingly, if my coworker creates the application on his machine, I can then use his application in my pkgbuild script and the installation succeeds. Both his application and the application I build on my machine are signed with the same company Developer ID Application and are notarized. Both applications also run on my machine and have the same functionality, as their source was pulled from the same branch. We are both using XCode 16.2. This problem only started to happen on my machine last week. Does the pkgbuild command have a cache that can be deleted? Thank you for your time.
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
Dear App Store Engineering Team, I am writing to request official confirmation regarding the behavior of App Store Server Notifications when migrating a live application from V1 to V2. Context: Our application has been live since 2008 and currently utilizes App Store Server Notifications V1. We have a large database of existing legacy subscribers. We are preparing to switch our Production environment setting in App Store Connect from Version 1 to Version 2. Our Questions: When we change the setting in App Store Connect to Version 2: Global Format Switch: Does this setting apply immediately to ALL notifications, including those triggered by subscriptions that originated years ago (legacy users)? Payload Consistency: Will renewals for existing legacy subscriptions continue to arrive in the JSON V1 format, or will they immediately start arriving in the V2 JWS (signedPayload) format? Our expectation is that the switch is global and all future notifications (regardless of subscription age) will be sent as
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
APNS
App Store Server Notifications
Notification Center
User Notifications