主app有2个扩展，主app的bundleID 有了家庭控制的分发权限，但是2个扩展申请了家庭控制的分发权限，一直没有给。导致我现在上传不了app到app store connect 中。一直在等待给权限！！！，app要等着发布

I have read many blogs and relevant posts on forums, but I still don't know what to modify or how to solve this problem. I'm extremely anxious now Guideline 2.1 - Information Needed We have started the review of your app, but we are not able to continue because we cannot locate the in-app purchases, such as 年会员 and 月会员, within your app at this time. Next Steps To help us proceed with the review of your app, please reply to this message providing the steps for locating the in-app purchases in your app. Note that in-app purchases are reviewed in an Apple-provided sandbox environment. Make sure they have been appropriately configured for review in the Apple-provided sandbox environment. If you are restricting access to in-app purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the in-app purchases for our review. Additionally, note that the Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect before paid in-app purchases will function. Resources Learn more about offering in-app purchases. Learn more about testing in sandbox.

I have read many blogs and relevant posts on forums, but I still don't know what to modify or how to solve this problem. I'm extremely anxious now Guideline 3.1.2 - Business - Payments - Subscriptions Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect. Next Steps Update the metadata to include the information specified above. Resources Apps offering auto-renewable subscriptions must include all of the following required information in the binary: Title of auto-renewing subscription (this may be the same as the in-app purchase product name) Length of subscription Price of subscription, and price per unit if appropriate Functional links to the privacy policy and Terms of Use (EULA) The app metadata must also include functional links to the privacy policy in the Privacy Policy field in App Store Connect and the Terms of Use (EULA) in the App Description or EULA field in App Store Connect. Review Schedule 2 of the Apple Developer Program License Agreement to learn more. Guideline 3.1.2 - Business - Payments - Subscriptions We noticed that one or more of your auto-renewable subscriptions is marketed in the purchase flow in a manner that may mislead or confuse users about the subscription terms or pricing. Specifically: The billed amount of your auto-renewable subscription is not clearly and conspicuously displayed to the customer. Next Steps Please revise your auto-renewable subscription purchase flow to ensure that the billed amount is the most clear and conspicuous pricing element in the layout. Any other pricing elements, including free trial, introductory pricing, and calculated pricing information, must be displayed in a subordinate position and size to the total billed amount. Factors that contribute to whether the billed amount is clear and conspicuous include, but are not limited to, the font, size, color, and location of the billed amount in the auto-renewable subscription purchase flow. Resources See design guidance for auto-renewable subscriptions in the Human Interface Guidelines, including how to create a positive onboarding experience. Learn more about offering auto-renewable subscriptions in your app.

审核回复：Issue Description The app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1. Specifically, the app still uses the ScreenTime API to hide apps. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed. 代码我都没有怎么改，然后之前2025年都上架成功了的，现在更新一个版本后，就不让上架了，是怎么回事？