Hi,I have a question around a specific use case. Let's say, user logged in via a non-Apple account (eg: Google) in my app and then the authentication tokens expires, so now the user has to be authenticated again when they launch the app. In this case, do we have to show both options Google sign in and Apple Sign in? or can we just show the previously selected auth method and let the user login. If we have to show both and user opts to sign in with Apple in our app's use case we will end up creating a new user account and the user will not be able to access any data linked to his original account. Can you please let me know if we can offer only the sign in for the account the user previously used or we have to offer Apple sign in also along with it. Thank You!Regards,Ashish

Hello, I want to provide in- app subscription option for my application services inside other apps. Is this possible? Does Apple in app subscription guidelines allow this? Reading the guidelines this use case is not clear. UseCase: I am embedding the services that my app provides inside other 3rd party apps (embed my application Framework/library within the other application) but want to provide in-app subscription option to use services provided by my library. Users can purchase this service by subscribing to monthly subscription option using Apple in-app subscription. Because there are multiple other 3rd party applications that will include my library and since these 3rd party applications in some cases are not from the same developer account I do not want to use individual in-app subscription for each application. Instead, I am looking for a way to create in-app subscription from my main application and provide the same purchase option within all other 3rd party apps that embed my application library. Can this be done? Does Apple in-app subscription allow this use case?