“translate scheme”

[quote='806866021, SD2000, /thread/806866, /profile/SD2000'] Is there any further documentation on implementing … ? [/quote] No. Note The original WWDC session that discusses this stuff, WWDC 2025 Session 10077 Replace CAPTCHAs with Private Access Tokens, is no longer available from Apple, but I’ve found that rummaging around on the Internet with the original URL (https://developer.apple.com/videos/play/wwdc2025/10077/) to be a fruitful exercise (-: [quote='806866021, SD2000, /thread/806866, /profile/SD2000'] or has the capability been deprecated? [/quote] That doesn’t follow. PATs are an industry standard thing. We don’t have Apple-specific documentation for that technology in the same way that we don’t have Apple-specific documentation for TCP. However, the history here is a bit tricky: There were originally two Internet drafts: Private Access Tokens and Privacy Pass: The Protocol. Those got merged into Privacy Pass Issuance Protocol. Which was standardised as RFC 9578 Privacy Pass Issuance Protocols. I als

I see, thank you. That's what I suspected but hoped there would be a better solution. Yes, they will. Are you saying that your watch app is the valuable bit, and the iOS app doesn't do anything without the watch app? Well, it's a fitness/workout app, and most users use the Watch to actually work out. The phone app is just for setup and checking your data. (workout is also possible but users prefer to use the watch) You didn't say whether the watchOS app is independent or not. Yes, my app is not independent. Not that I can think of, aside from communicating that watchOS 11 will be required with the next version of the app. Communicating the requirement of watchOS 11 (regardless of the channel) won't be noticed by all users running watchOS 10. Hence, many auto-updated iOS apps will render the app useless to most of these users. To conclude: The only proper workaround is to make the watch app independent, so users on older hardware can keep the older version. Correct? (I'm aware that making the app independent w

[quote='806580021, tczhu, /thread/806580, /profile/tczhu'] our app can only run on the Rosetta simulator [/quote] I want to make a couple of things clear: This isn’t a supported configuration. Honestly, I’ve always been surprised that this works at all. Apple has announce a timeline for the removal of general support for Rosetta. For the details, see the Important box at the top of About the Rosetta translation environment. I encourage you to work with your third-party SDK vendor to resolve this roadblock sooner rather than later. As to your immediate issue, if you create a small test project and run it natively in simulator, does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

@DTS Engineer it seems like .crash-files gets translated into text-file... so I can no longer attach it. I will try to upload it and share a link instead...

That sample doesn't quite work out of the box. Here is how you can get it to work on macOS 26 with Xcode 26 (and earlier versions of both, but that's what I'm using). Download the sample from https://developer.apple.com/documentation/driverkit/communicating-between-a-driverkit-extension-and-a-client-app?. Follow only some of the directions under Configure the sample code project: (turn off SIP) - skip this, it is no longer necessary Set Automatically manage signing for both the driver and the app targets Select a development team. Xcode will tell you that you cannot select an individual for this type of signing. ignore the advice about Sign to run locally and AD_HOC_CODE_SIGNING_ALLOWED. ignore all the other stuff. You don't need to make profiles, add capabilities, manually download profiles or add them to Xcode. Now go the Build Settings for the driver and app target, and change the Product Bundle Identifier. The download project uses a disambiguation string that doesn't work, and you end up with very long b

There's no macOS-like menu bar when the user chooses Full Screen Apps. I didn't know this and some of my app's functionality can only be accessed through the main menu bar. So I was thinking I could show some alternative way to access those features when in that mode. iPadOS has supported the ability to open a new scheme through drag and drop using UIDragItem and NSItemProvider and dragging it to the edge of the screen. When a user chooses Full Screen Apps, this no longer works for opening a new scene. I'd like to disable the drag and drop if it's not going to actually do anything. Those are two main things I can think of so far that depend on the user's choice of multitasking mode.

Is there no solution for this? I checked your other thread as well. Is there a way for me to remove the third party libraries from my SDK? I run the below commands to generate the SDK. xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS Simulator -archivePath BuildArtifacts/iossim.xcarchive | tee build.log xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS -archivePath BuildArtifacts/ios.xcarchive | tee build.log xcodebuild -create-xcframework -framework BuildArtifacts/iossim.xcarchive/Products/Library/Frameworks/AbcSDK.framework -framework BuildArtifacts/ios.xcarchive/Products/Library/Frameworks/AbcSDK.framework -output Frameworks/AbcSDK.xcframework As soon as I run, it gives me the list of resolved source packages that includes all the third party libraries. If I try removing the libraries, it gives error at all the import statements in my code. I even

Hello - here are recommended steps for testing App Store Server Notifications: Enter a URL for SANDBOX notifications in App Store Connect Create Sandbox test user(s) in App Store Connect In Xcode, ensure your build Scheme is set to Options > StoreKite Configuration = None, then run your build from Xcode on a connected device (you cannot test these steps running build on Simulator from Xcode). Proceed to make a purchase in your app. If you are not already signed in to your Sandbox test user on the device (under Settings > Developer > Apple Sandbox Account), you should be prompted to sign in after selecting the product to purchase in your app. IMPORTANT: when the purchase payment sheet loads, confirm that it says SANDBOX and then complete the purchase. The successful Sandbox purchase will trigger the App Store Server Notification being sent to the URL specified in first step above. You can also use the App Store Server API to get Notification History (including for Sandbox). Outside of using X