I found this Apple video and that answer my questions:
https://developer.apple.com/videos/play/tech-talks/110150/
ATMooee
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Hong Kong SAR, China
Post
Replies
Boosts
Views
Activity
In fact, what we suppose to offer is 1. for new subscriber (exclude certain user group say group A users - note: they are new subscriber), will has free trial and then normal subscription price. 2. for group A users, if within promotion period, will has discounted subscription price, otherwise will treat as new subscriber that has free trial and then normal subscription price. Base on this offer requirement, we choose to use introductory offer + offer code. However, as offer code can't test in sandbox and so we are not sure what is the exact flow of it and our implementation idea is work. That's why ask here. We do think about fire DTS and ask our question there, but it requires a project ready to illustrate the issue which is not suitable for our question.
Thanks, I tried cancel the free trial subscription in sandbox and Apple will send subscription EXPIRED notification to our server later.
Thanks eskimo, base on your information, I just need to choose 'Do Not Embed' for the OpenSSL.xcframework in 'Frameworks, Libraries, and Embeded Content' will keep my app run on iPhone / M1 simulator and submit without issue to AppStore Connect.
It is because I follow instructions in https://github.com/x2on/OpenSSL-for-iPhone on how to make openssl work on iphone and mac M1 xcode simulator.
I guess you will work on iOS 17.0 (21A5319a) (beta 7) and watchOS 10.0 (21R5349b) (beta 7) as my code becomes no problem on these version. So it is only bug on early beta version.
It becomes work on iOS 17.0 (21A5319a) (beta 7) and watchOS 10.0 (21R5349b) (beta 7). So it is only bug on beta version.
I posted a post with title: "How to use CMBatchedSensorManager" on how to use deviceMotionUpdates(), as there is no reply, so I fire a DTS and the support reply there is so far so solution on that. So I guess the api is remain not workable up to iOS 17 (21A5277j)
i.e. 3-party password manager apps can save and offer passkeys on iOS, iPadOS, and macOS by using new api.