User Profile

Hey Developers,I know these forums are more for technical questions and support, but I was hoping some of you could post examples of Independent Watch Apps, ideally with Apple Sign-In. Your own, or others you admire.We have been seeing a lot of weirdness with Apple sign-in and been getting interesting error cases when a tester jumps between Apple IDs on the same device. I'd love to see how other apps handle Apple Sign-in on the watch, partly to help see what issues are ours, and what are part of Watch OS.I'll post ours in the next few weeks when we launch.Thanks in advance.

Are are using Apple Sign-In on an independent watch app, and have found with our internal testing that on the initial Sign-In the user is prompted with "EMAIL OPTIONS" to "Share" or "Hide" their email, however on subsequent Sign-Ins they no longer get this option, just a message saying: "Do you want to sign in to [app name] with your Apple ID [email address]?" - "Continue" being the only option. Fresh installs, revoking apple SIgn-In, logging out and back in of the user's Apple ID account, none of these fix the issue once it appears. The only way I have found to get the user back to their original state, is by making a build with a new bundle ID. Has anyone else come across this issue, or know how a user can get themselves into this state? I looked for an option like "Always Hide Email address", but I haven't found it yet. Thanks,

I'm curious about what Apple's Review team are looking for in regards to Privacy policies on Independent Watch Apps.With regular apps we have found the review team looks for:Privacy Policy in the Apple Connect metadataPrivacy Policy and Terms and Conditions on the first view, readable before the user creates an account/logs inPrivacy Policy and Terms and Conditions accessible in-app while logged in (generally in an options menu)However with an independent app on apple watch, only the first of those points are easily possible. Adding labels for Policies on the watch before Apple Sign-in clutters things up, but also it isn't really practical to read them on the watch. We have entertained the idea of emailing the user the policy, but this is not practical to do until the user creates an account and we get theri email via Apple Sign-In.Has anyone out there come up with some Best Practices for managing these types of experiences? We can easily bury the policies in an options menu, but we want to make sure our users have every opportunity to read and accept them, especially when looking for GDPR compliance. Thanks,