Furuno AP(EW750) is sending EAPOL M1 message, but Iphone16 is not responding with EAPOL M2 message, Hence Iphone16 is unable to connect to Qualcomm based AP with MLO suiteb encryption. Issue impact: All the Iphone16 users cannot connect to WiFi7 AP with MLO suiteb encryption globally. Predominantly, Iphone users tend to connect to more secured wifi networks using WPA3 suiteb encryption, hence many of the iphone users will experience the connectivity issue significantly. Topology: AP Hardware: Furuno WiFi7 AP(EW770) The Furuno WiFi7 AP uses Miami IPQ5332 with waikiki radio QCN9274 (Qualcomm based chipset) AP software: SPF12.2 CSU3 IPhone16 software: (18.3.1 or 18.5 ) I phone16 wifi capabilities: 802.11 b/a/g/n/ac/ax/be Radius server details: Radius server: Laptop running with Ubuntu Radius package: 3.0.26dfsggit20220223.1.00ed0241fa-0ubuntu3.4 Version: 3.0.26 Steps: Power on the Wi-Fi 7 Access Point with the Miami chipset, and flash it with the SPF 12.2 CSU3 image. Enable both 5 GHz and 6 GHz radios o
Search results for
missing package product
50,215 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Touch Bar items: Jump to destination and Ident missing and Customise Touch Bar unavailable in Xcode 26.0 (17A324).
Topic:
Developer Tools & Services
SubTopic:
Xcode
[quote='857997022, lucky06, /thread/799833?answerId=857997022#857997022, /profile/lucky06'] send the demo project and app [/quote] I took a look at that today and I’m confused by your starting point. My general advice when building Mac software is to do your day-to-day development using Apple Development signing. Then, once you have things working, you can export your app using the signing appropriate for your distribution channel (Apple Distribution for the Mac App Store, Developer ID for direct distribution). See The Care and Feeding of Developer ID for more about this. If you do that then you only need to worry about the -systemextension stuff at the final step, when you export your product for distribution. And when you stick with Apple Development signing you can rely on Xcode’s automatic code signing to do the right thing. However, you seem to be trying to use Developer ID signing for day-to-day development. This is a mistake, and it’s causing you grief here. So, for example, I opened your proj
Topic:
App & System Services
SubTopic:
Networking
Tags:
OK, a quick update… IMPORTANT Please don’t post replies that just say ‘me too’. There’s a Boost button at the top of the thread that you can click in that case. OTOH, if you have new info to share, please post a reply, not a comment. It’s hard for me to keep track of comments. My understanding of this issue is that: It was a problem with the way that the Developer website issued provisioning profiles. It had been resolved at the time I posted that response, about 4:00 Pacific time. Hence my original advice on this thread to run a test with a new, unique bundle ID. I just ran that test myself and I didn’t see a problem. Specifically: Using Xcode 16.4 on macOS 15.6.1, I created a new project from the iOS > App template. In Signing & Capabilities, I confirm that automatic code signing was enabled with my team selected. I selected an iOS 18.6.2 device as the run destination and chose Product > Run. The app ran just fine. However, this is using my extant wildcard provisioning profile, so it’s no
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I'm trying to use FSKit to create a File System Extension that can read MFS-formatted disk images, following the old MFSLives sample project for reference. I have a well-formed MFS formatted img file that I'm trying to mount, but I'm having trouble getting the system to actually use my FSModule. DiskImageMounter fails to mount the img file, but I'm able to use it to attach the image as a device by clicking Ignore when it prompts me that it isn't able to read the disk. This is effectively the same as using the hdiutil command in Terminal. hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount Sample.img I've read that FSKit isn't fully integrated with Disk Arbitration yet, so I decided to see if I could force the system to use my extension by using the mount command. mkdir /tmp/Sample mount -F -t MFS disk54 /tmp/Sample Watching the logs in Console, I can see that fskit_agent sees my extension in its New Modules List, and I see an MFS process gets launched and logs messages from com.apple.running and c
I have successfully configured Apple-hosted Asset Packs for my app and uploaded them through App Store Connect. The status currently shows READY FOR INTERNAL & EXTERNAL TESTING. However, I don’t see any option to submit these Asset Packs for review and distribution. Could anyone confirm the correct process for submitting Asset Packs for review, or let me know if there’s an additional step I may have missed in App Store Connect?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
ApplePaySession.applePayCapabilities() started returning applePayUnsupported in third-party browsers
We rely on ApplePaySession.applePayCapabilities() to decide whether to show the Apple Pay button. We use two different merchant IDs for non-prod/prod environments, and encountered a change in behavior where this API now returns different results. These merchant IDs are generated from a third-party provider Adyen. However, Adyen has informed us that they are unable to identify the root cause of the issue and advised us to seek assistance directly from Apple Pay support. Timeline Last known working date: 13/08/2025 Issue first noticed: 18/08/2025 Environment Details Apple Pay JS API version 1.latest Browsers Tested: Third party browsers including Chrome/139.0.0.0, Firefox/141.0 Browsers with ApplePaySession built-in (like iOS Chrome, iOS Safari, and macOS Safari) are working fine Framework Stack: Angular v18.1.3 (important) no configuration setup in Apple dev account, merchantId is generated from a third-party provider Adyen. Current Execution Flow: Apple Pay JS API script element is injected Triggers below to
In the archived documentation for Distribution Definition files (https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html), the allowed-os-versions and os-version element are partially documented. I have a few questions about these elements: allowed-os-versions The documentation states: Availability: Available in OS X v10.6.6 and later. Has this element always worked correctly in the past? I'm asking because it does not seem to work correctly on OS X v10.14 for the min attribute of a sub os-version element. os-version The documentation states: This element is designed for you to use a specific OS version number for the min attribute, and a major OS version number for the before attribute. The expectation is that you will know an exact minimum version but not an exact major version. This keeps you from having to guess the last minor revision before the next major revision, as you would have to do if the before attribute were
Hi everyone, I’ve been receiving App Store Server Notifications (webhooks) normally for a specific transaction. Everything was working fine — I could use the original_transaction_id to query transaction history, and transaction_id to look up specific transactions. However, starting recently, all API calls for that transaction (both Get Transaction Info and Get Transaction History) now return not found. • The webhooks used to arrive normally for this transaction. • I am sure I’m querying the correct environment (production vs sandbox). • The IDs I’m using are exactly the ones from the last webhook payload. • I haven’t changed my integration code. My questions: 1. Under what conditions does Apple’s API return “not found” for original_transaction_id that previously worked? 2. Can Apple actually purge transaction records (in production)? 3. Could this happen due to refunds, revocations, or other account actions? 4. Is this expected behavior, or should I file a DTS (Technical Support Incident)? A
Hello, I have an iOS app built using the .NET 8 iOS framework, and I'm encountering a puzzling issue: the app crashes immediately on launch, but only for some users. What We Know: The crash is not device or OS-specific. It affects a few users on iPhone 14 and iPhone 15, across various iOS versions (e.g., 17.7, 18.5, and even the latest). Other users with identical device and OS specs are able to run the app without issues. The crash only occurs when the app is installed via App Store or TestFlight. If the same IPA is distributed via a third-party tool like Updraft, the app runs fine for affected users. This suggests the issue may be related to code signing or packaging during submission to App Store Connect. What We've Tried: Added additional exception and error handling in didFinishLaunchingWithOptions. Experimented with build settings, including enabling AOT compilation. Reviewed crash logs and symbolicated them using atos. Crash Log Snippet: Here’s a portion of the lastExceptionBacktrace from the
Topic:
App Store Distribution & Marketing
SubTopic:
General
So I'm developing an ios application which should be showing shortcuts, but its not. I'm not sure how to debug why the functionality isnt working. Believe I'm correctly calling AppShortcutsProvider's updateAppShortcutParameters, but I dont see any errors in the console showing me a problem. And in fact, I made a simplified just swift version that works before I tried to integrate it into a more complex project. But now I'm at a loss as to what is going wrong or what debug tools I can use to figure it out. Any help would be appreciated. When building my project I see: 025-08-18 14:07:49.371 appintentsmetadataprocessor[57506:35387547] Starting appintentsmetadataprocessor export 2025-08-18 14:07:49.414 appintentsmetadataprocessor[57506:35387547] Writing Metadata.appintents 2025-08-18 14:07:49.414 appintentsmetadataprocessor[57506:35387547] Metadata root: /Users/jpetersen/Library/Developer/Xcode/DerivedData/Unity-iPhone-dtnhxevagfkzsjdavesziaqrwisr/Build/Products/ReleaseForRunning-iphoneos/Unity
I have created a sample app which read/write from a network file. When the file was attempted to open (using open Linux API), connection to network file was lost. The thread which was stuck on the open method, returns after a long time. It was observed that for macOS, the maximum return time of the thread was around 10 mins, whereas in Windows and Linux, the maximum timeout was 60 sec and 90 sec. macOS has a very large timeout before returning the thread with a network failure error. Is this by designed and expected? With a large timeout as 10mins, it's difficult to respond swiftly back to the user.
Hello everyone, My app was recently rejected under Guideline 4.1 – Design: Copycats. The review team mentioned that my app or its metadata appears to be misrepresenting itself as another popular app or service, and therefore was not approved. This came as a surprise, because my app is an original trading journal product that I’ve built from scratch. While there are other trading journals in the market, my app has unique features and a different design. I did not intend to copy or impersonate any existing app. I would really appreciate advice from anyone who has gone through a similar rejection: What kind of changes did you make to get past this rejection? Should I focus more on branding (name, logo, color scheme) to differentiate? Is it helpful to write an explanation to the App Review team describing how my app is unique? Any tips or experiences would be very helpful, since I want to make sure my app stands out clearly and avoids any resemblance issues. Thank you in advance!
Hello everyone, Today we suddenly received a Pending Termination Notice for our Apple Developer account. What makes this situation especially difficult is that there were no prior warnings, rejections, or requests for clarification before this action was taken. Our app was published on September 1, and just a short while ago (September 12) we were notified that the account is flagged for removal and our product was already taken down from the App Store. We submitted a formal appeal to the App Review Board a few minutes ago, but we are extremely concerned. Our company is a U.S.-registered business and we provided all required documentation during enrollment and afterwards. Everything is legitimate, and we strongly believe this is a mistake. For us, every minute matters — we run a large-scale marketing campaign, and each delay is already costing us thousands of dollars in losses. This sudden removal without prior communication feels devastating. Has anyone else faced a similar situation? How l
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Same issue Xcode 26 (17A321), I've added FB20258577 with icon composer file and the inspector settings per layer. By blur do people mean Liquid Glass effects? Otherwise we have normal blend mode. The only way I was able to get a build uploaded today to fix my missing icon on the iPad target was to delete this file altogether. I have no idea why the iPhone target worked at all. Xcode Cloud was building for 2 hours today with no feedback. I finally archived myself and saw the validation errors with the red herring of it being in an asset catalog. So very tired but happy to have worked on betas again. I gave up on that when iOS 5 iCloud builds crashed every other launch and I had to revert three months of work. Not reverting Liquid Glass. It has issues, but it's very pretty when you give it a chance. It was inspiring to work with something beautiful amongst all the ugliness in the world these days.
Topic:
Developer Tools & Services
SubTopic:
Instruments
Tags: