A Summary of the WWDC25 Group Lab

Thanks for the extra info. First up, an SFAuthorizationPluginView can’t support smart card authentication in the same way as the built-in login UI can (FB11978008). That’s because the built-in UI populates various authorization context values but SFAuthorizationPluginView does not. The name and format of these values is not documented, so the authorization plug-in can’t work around this issue itself. However, that’s not what you’re trying to do. Rather, you’re trying to simply use smart-card-back credentials, and that’s more feasible. There’s one thing to check here, and then a roadblock to get around. The thing to check is that your smart card is available in pre-login context. To do that, disable your authorisation plug-in, reverting to the built-in login UI. Then check that you can use the built-in PIV smart card support to pair your user with your smart card, and thus log in with your YubiKey. I don’t have docs for how to do that handy — that’s more of an Apple Support thing than a DTS thing — but I do it

[quote='871873022, White_Nebel, /thread/812348?answerId=871873022#871873022, /profile/White_Nebel'] FB20753534 [/quote] Thanks for that. I took a quick look [pun intended :-] and there’s nothing to report on that front. With regards Greg’s point, I guess that your key concern is that: On iOS 26 it’s trivial for users to grab your AR content. On iOS 18 it was still possible — there are a bazillion apps on the App Store that let you download files from the Internet — but it wasn’t trivial. Is that an accurate summary? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've consulted the local Apple Contact Us group. They replied last week that 'Prepare for Submission' is indicative of missing information. I already know that since this app submission is about 250th with IAPs. Then he or she said that my subscription plan may not have a screenshot. That's the case, either. They often try to solve an issue with a guess, which leads nowhere.

I'm in the same shoes since the end of the last December. Because my app contains the Japanese localization package, I thought I was not able to have subscription plans due to the holiday season and the Japan MSCA. But an Apple local rep. says that's not the case. I already released the app by reducing features. In the near future, I want to add subscription plans since it currently has no mineralization mechanism whatsoever. At this moment, it seems that I've reached the end of the rope. Seeing the last submission with subscription plans, I don't see anything wrong with the app in question. Also, I have deleted an existing sub group with a new one once or twice with no resolution.

Isn't it just the matter of creating a new subscription group with a new set of product identifiers? You should have switched to the manual release as opposed to auto release and then submit a software update when you decided not to release the initial version. You have made the initial group of product identifiers useless, I guess.

I try to update remoteHandle using CXCallUpdate for outgoing calls, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). What's actually not working here? Are you looking at what the lock screen UI shows or what you see in other locations (particularly in the Recent call list)? There is a longstanding issue (r.126348631) where call updates aren't being displayed on the lock screen interface; however, this is purely about UI showing old data, not about the update itself completely failing. Notably: I use this handle value to implement recall by tapping on a call in the Recents tab of the system address book. But since my calls can transform from p2p to group calls, I need to update the handle value or find some other way to pass call identification info. ...I'd expect this sort of thing to work exactly the way you need/expect, regardless of what the lock screen UI shows. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@DTS Engineer Thank for your answer. In summary, our issue is not straightforward. On the application site, everything functions correctly. The problem lies on the client (browser) side. I am uncertain whether a race condition or a similar condition may be the cause of this issue. All of our JavaScript code executed for this purpose is synchronous, resulting in no concurrency. The problem occurs precisely at the moment when this code executes: “window.location.assign” Therefore, there is nothing complex about it. We are simply redirecting the current page to the Universal Link. This operation works fine in most conditions but doesn't when the same Safari tab is being used. We do not see any errors in the Browser javascript console. Our flow will not function without JavaScript, as it is the only option to automatically redirect to the Universal Link without user interaction. Perhaps the issue is not with the Universal Link itself, but rather with the browser, which is unable to properly handle the li