blocks|key|571916|text|了解拒收原因|type|unstyled|depth|inlineStyleRanges|entityRanges|data|571917|通常，在购买流程中有三个位置会导致大多数App拒绝：|571918|获取产品的问题|ordered-list-item|571919|采购中的错误|571920|购买后未解锁的内容|571921|通常，审查员会包括一个截图，上面写着他们遇到的问题。这可以帮助您找到在您的应用程序中查找问题的位置。始终尝试在本地构建或测试中首先重现问题。RevenueCat在您的环境和评审员中的行为将是相同的，所以如果您的集成有任何问题，它应该能够被复制。|571922|571923|通常情况下，在Sandbox和Testflight中购买会很好，但是将无法获取产品。重要的是要确保您的产品包括您的应用程序，以供审查。如果应用程序尚未被应用程序商店批准，则应用程序内购买产品必须与您的第一次应用程序评审一起提交。|571924|​|571925|📷|atomic|offset|length|571926|571927|不要忘了将产品提交给你的应用程序的第一个版本，其中包含应用程序内的采购。|571928|如果您已经发布了包含应用程序内购买的应用程序版本，您可以在中创建新产品，而不必发布对应用程序的更新。您将不得不提交新产品审查独立于新的应用程序版本，它们必须处于“批准”状态，然后才能购买。|571929|如果在Testflight或本地构建中获取产品有困难，下面是一篇关于最常见的原因是的好文章。|571930|571931|如果在使用RevenueCat的采购过程中发生错误，它将是错误处理指南中概述的错误之一。了解是什么错误触发了拒绝，这是确保问题得到解决的唯一方法。|571932|如果审阅者提供了一个错误的屏幕截图弹出-使用它来帮助跟踪问题。RevenueCat本身将永远不会显示面向用户的弹出或错误消息，所以查看您的应用程序，找出触发警报的代码，并向后工作以确定错误消息。|571933|“无法连接到iTunes商店”|571934|这实际上是苹果为所有SKErrors使用的通用错误消息，而不是来自RevenueCat的错误消息。有关更多信息，请参见他们的错误处理指南。|571935|STORE_PROBLEM+--“应用商店出了问题”|571936|这是RevenueCat中最常见的错误，可能导致无法解释的App拒绝。不幸的是，当苹果的沙箱环境关闭，无法验证购买时，就会出现此错误。这里最好的做法通常是重新提交你的二进制文件，或者尝试向评审员解释情况。|571937|沙箱中经常会有短暂的停机，但偶尔也会导致一次能维持几天中断.|571938|571939|即使在购买过程中没有问题，您的应用程序也可能被拒绝，但是在购买之后，内容不会被解锁。您应该能够在测试环境中重现此问题。|571940|买完后再检查一下你是否是正确检查订阅状态。|571941|其他窍门|571942|审查员提供了“下一步”|571943|通常情况下，评审人员会向您提供“下一步”来解决拒绝问题，就像他们在这里所做的那样。这些通常对找出采购中的任何问题没有多大帮助。|571944|如果您正在使用RevenueCat，沙箱和生产采购将自动处理，因此即使评审人员提供了此原因，这也是不正确的。|571945|应用程序拒绝太糟糕了:(|571946|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/ec0fd87e4bf9f608f2c51c8967aa8e43.png|imageAlt|1|LINK|MUTABLE|url|https://support.revenuecat.com/hc/en-us/articles/360041793174-Why-are-my-products-offerings-or-available-packages-empty-|2|https://docs.revenuecat.com/docs/errors|3|https://developer.apple.com/documentation/storekit/skerror|4|5|https://status.revenuecat.com/incidents/6y3tfs3fyxb7|6|https://docs.revenuecat.com/docs/purchaserinfo^0|0|0|0|0|0|0|0|0|0|0|1|0|0|0|0|0|Y|7|1|0|0|T|6|2|0|0|0|A|8|3|1Q|6|4|0|0|0|K|7|5|0|0|0|C|8|6|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|2M|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|2N|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|2O|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|2P|8|@]|9|@]|A|$]]|$1|M|3|E|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|2R|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2S|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|2T|8|@]|9|@$U|2U|V|2V|1|2W]]|A|$]]|$1|W|3|Q|5|6|7|2X|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|30|8|@]|9|@$U|31|V|32|1|33]]|A|$]]|$1|13|3|H|5|6|7|34|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|35|8|@]|9|@$U|36|V|37|1|38]]|A|$]]|$1|16|3|17|5|6|7|39|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|3A|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|3B|8|@]|9|@$U|3C|V|3D|1|3E]|$U|3F|V|3G|1|3H]]|A|$]]|$1|1C|3|1D|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|3J|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|3K|8|@]|9|@$U|3L|V|3M|1|3N]]|A|$]]|$1|1I|3|J|5|6|7|3O|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|3Q|8|@]|9|@$U|3R|V|3S|1|3T]]|A|$]]|$1|1N|3|1O|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|3X|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|1X|3|-4|5|6|7|3Z|8|@]|9|@]|A|$]]]|1Y|$1Z|$5|20|21|22|A|$23|24|25|-4]]|26|$5|27|21|28|A|$29|2A]]|2B|$5|27|21|28|A|$29|2C]]|2D|$5|27|21|28|A|$29|2E]]|2F|$5|27|21|28|A|$29|2C]]|2G|$5|27|21|28|A|$29|2H]]|2I|$5|27|21|28|A|$29|2J]]]]

<h2>Understanding the rejection reason</h2>

<p>There's usually three places in the purchase flow that cause the majority of App Store rejections:</p>

<ol>
<li>Issues fetching products</li>
<li>Error during purchase</li>
<li>Content not unlocked after purchase</li>
</ol>

<p>Usually the reviewer will include a screenshot with the problem they encountered. This can be helpful for you to track down where to look for the problem in your app. Always try to reproduce the issue first in a local build or Testflight. RevenueCat will behave the same way in your environment and the reviewers, so if there's any problem with your integration it should be able to be reproduced.</p>

<h2>Issues fetching products</h2>

<p>Often times, purchases will work fine in Sandbox and Testflight, but App Store Review will not be able to fetch products. It's important to ensure that you are including your products with your app for review. If an app has not already been approved for the App Store, the in-app purchase products must be submitted with your first app review.</p>

<p><a href="https://i.stack.imgur.com/g123F.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/g123F.png" alt="Don&#39;t forget to submit the products with the first version of your app containing in-app purchases"></a></p>

<p>Don't forget to submit the products with the first version of your app containing in-app purchases</p>

<p>If you've already released a version of your app containing in-app purchases, you can create new products in App Store Connect without having to release an update to your app. You'll have to submit new products for review independently of a new app version, and they must be in the 'Approved' state before they'll be available for purchase.</p>

<p>If you're having trouble fetching products in Testflight or a local build, here's a good article with <a href="https://support.revenuecat.com/hc/en-us/articles/360041793174-Why-are-my-products-offerings-or-available-packages-empty-" rel="nofollow noreferrer">the most common reasons this occurs</a>. </p>

<h2>Error during purchase</h2>

<p>If an error occurs during the purchase process with RevenueCat, it will be one of the errors outlined in the <a href="https://docs.revenuecat.com/docs/errors" rel="nofollow noreferrer">Error Handling guide here</a>. Understanding what error triggered the rejection is the only way to make sure the issue gets resolved. </p>

<p>If the reviewer provides a screenshot of an error popup - use that to help track down the issue. RevenueCat itself will never display a user-facing popup or error message, so look through your app to find the code that triggered the alert and work backwards to determine the error message.</p>

<h3>"Cannot connect to iTunes Store"</h3>

<p>This is actually the generic error message Apple uses for all <a href="https://developer.apple.com/documentation/storekit/skerror" rel="nofollow noreferrer">SKErrors</a> and not an error message from RevenueCat. See their <a href="https://docs.revenuecat.com/docs/errors" rel="nofollow noreferrer">guide on Error Handling</a> for more info.</p>

<h3>STORE_PROBLEM - "There was a problem with the App Store"</h3>

<p>This is the most common error from RevenueCat that can lead to unexplained App Store rejections. Unfortunately, this error occurs when Apple's sandbox environment is down and unable to verify purchases. The best course of action here is usually to re-submit your binary or try to explain the situation to the reviewer.</p>

<p>There are frequent, momentary outages in sandbox from time-to-time, but occasionally outages <a href="https://status.revenuecat.com/incidents/6y3tfs3fyxb7" rel="nofollow noreferrer">can last for days at a time</a>.</p>

<h2>Content not unlocked after purchase</h2>

<p>Your app could also get rejected even if there are no issues during the purchase process, but the content does not get unlocked after purchasing. You should be able to reproduce this issue in a test environment. </p>

<p>Double check that you're <a href="https://docs.revenuecat.com/docs/purchaserinfo" rel="nofollow noreferrer">checking the subscription status correctly</a> after a purchase.</p>

<h2>Other Tips</h2>

<h3>Reviewer provided "Next Steps"</h3>

<p>Often times, the reviewer will provide you with "Next Steps" to resolve the rejection as they've done here. These are usually not the most helpful in pinpointing any issues with purchases.</p>

<p>If you're using RevenueCat, sandbox and production purchases are automatically handled so even if the reviewer provides you with this reason, it's simply incorrect.</p>

<p>App rejections suck :( </p>


<p>So I implemented an auto-renewing subscription on my iOS app using RevenueCat's SDK. </p>

<p>Quoting from their website,
<a href="https://medium.com/revenuecat-blog/getting-through-app-review-39ac50438c62" rel="nofollow noreferrer">https://medium.com/revenuecat-blog/getting-through-app-review-39ac50438c62</a></p>

<blockquote>
  <p>Improper use of sandbox vs production validation environments
  Developers often get sideways when submitting an app the makes use of Apple’s /verifyReceipt endpoint. Sometimes devs will configure the release version of their app or backend to point only at the production IAP environment. Doing this fails in App Review because the reviewers use the sandbox environment for testing. RevenueCat makes this a non-issue.</p>
</blockquote>

<p>Everything was tested fine on Sandbox through Xcode "run" and TestFlight releases, but apparently it failed when the app reviewer attempted at it. </p>

<blockquote>
  <p>We found that your in-app purchase products exhibited one or more bugs
  when reviewed on iPhone running iOS 13.5.1 on Wi-Fi.</p>
  
  <p>Specifically, your app displays an error message when we attempt to
  purchase your subscription.</p>
  
  <p>Next Steps</p>
  
  <p>When validating receipts on your server, your server needs to be able
  to handle a production-signed app getting its receipts from Apple’s
  test environment. The recommended approach is for your production
  server to always validate receipts against the production App Store
  first. If validation fails with the error code "Sandbox receipt used
  in production," you should validate against the test environment
  instead.</p>
</blockquote>

<p>Anyone has any experience with getting through this? I've just gone through revenuecat's documentation one more time and my code sees to be in order. Thanks</p>


App using RevenueCat got rejected in review

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

因此，我使用RevenueCat的SDK在我的iOS应用程序上实现了自动更新订阅。引用他们的网站，不恰当地使用沙箱和产品验证环境时，开发人员在提交应用程序时往往会侧身使用苹果的/verifyReceipt端点。有时候，devs会将其应用程序或后端的发布版本配置为只针对生产IAP环境。在App中执行此操作失败，因为评审人...

使用RevenueCat的应用程序在审查中被拒绝-腾讯云开发者社区-腾讯云

问使用RevenueCat的应用程序在审查中被拒绝
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用RevenueCat的应用程序在审查中被拒绝EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用RevenueCat的应用程序在审查中被拒绝
EN