Apple Maps Guides

I'm also having this problem. I signed the Apple Developer Program License Agreement Updated earlier, and I still see banners saying I need to sign it, and cannot update any apps. But none of the normal links to sign agreements are working. I sent an email to support, we'll see what happens.

Hi Quinn @DTS Engineer I am curious if my post is missing any information needed to troubleshoot my issue. I searched through the forums and online and haven't found my specific issue anywhere. The more I think about it I come to the following: true peer to peer with no wifi network works with iOS devices without cellular (so AWDL is used) once cellular is introduced there needs to be a wifi network because using AWDL is not an option Maybe some kind of option can be passed into the NetworkListener or when creating a NetworkConnection that would prompt apple's code to try to use AWDL if the peer to peer option is true? [quote='867952022, DTS Engineer, /thread/808917?answerId=867952022#867952022'] Share and Enjoy [/quote]

ok I've managed to get it all working correctly (following from my earlier comment) I went through the checklist posted by Apple Engineer above the TechNote checklist at: TN3186: Troubleshooting In-App Purchases availability in the sandbox | Apple Developer Documentation The thing that was blocking the products being returned in array was having not filled in ALL of the details needed on the AppstoreConnect > Business page Namely payment agreement, bank account, tax status statements etc. After I had done that, about 2 hours later, all my test calls and purchasing views were working and the whole purchase flow as usual for an iOS device See attached for Sandbox confirmation Apparently all Business info is needed even for Sabdbox transactions. HTH folks. Shout if I can add any more info

All the documentation I was able to consult says that macOS is designed to use up to all available storage on the startup disk (which is the one I am using since I have only one disk, and the available space aforementioned reflects this) for swapping when physical RAM is not enough. Sure, that's what the system will do. Strictly speaking, it will actually start warning the user and then automatically terminating processes as it approaches full, but it will basically use all available storage. However... Then why is the process killed long before the swapping area is exhausted? ...the fact that the system is willing to use all available storage doesn't mean that it should let any random process do that. Every process on the system has its own memory limit (both address space and used pages) enforced by the kernel. I'm not sure what the default limit is... once about 40 or so... ...however, 40 GB doesn't seem like a terrible default. Keep in mind that the point of the default isn't simply to prevent the drive f

Maybe I posted too soon because despite the text updating to say App Store and Apple accepting the upload it fails: This was after many attempts to upload with timeouts and other strange errors messages with all three of our apps - I suspect from many of us were try to upload and it overloaded the servers. And then... Apple reverted the text to remove the App Store. So something is clearly wrong at their side.

Can you confirm that this is happening in macOS 15.7.3 (24G416) in upload a new sysdiagnose if it is? It is, unfortunately, still happening in a macOS 15.7.3 (24G416) VM I'm testing in. I attached a new sysdiagnose to FB21305906. I don't know what (if any) user interface you've implemented, but having some kind of app experience running while your volume is mounted would be the most direct way to prevent these issues. Hmm, ok. So presumably if I just wait for a fix I might be waiting for a while. Right now my own UI is just a guide to enable the file system extension, so there's essentially no reason at the moment for users to keep the app itself open after that point. It's pretty much just in an app because it's necessary for distribution. Maybe I could have some GUI-less mode of the app open whenever the extension mounts something and then kill that instance on unmount? But between sandboxing and App Review complications I don't know if that's actually feasible.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

I have the exact same issue and setup as the OP. All configured as per the Apple docs. Consistently getting zero products returned. Plus, on real device Settings > Developer > Sandbox > Manage > Initiate Purchase fails with incorrect Bundle and/or Prodict ID, but says Could not complete at this time, please try later with correct Bundle & Product ID. Later being 3 days so far for me... Any help please?