Whenever they get around to the manual review, they'll either approve and republish, or request changes. The only time you'll ever receive any feedback from an actual human being, is when they perform a manual review and request changes. Stable is still sitting in the dashboard, unpublished, pending review. Our best guesses as to any issues they might have had with that particular update have already been addressed, but they won't allow us to submit a new update till the pending one is manually reviewed.īottom line, CWS does whatever the hell it wants, whenever the hell it wants, and there's essentially no meaningful communication about most of these decisions. We got a canned response from CWS a few days ago which kinda pretends it's from a real person, but doesn't even address the removal, or give any kinda concrete explanation about anything. What doesn't make any sense, is that they unpublished the previously approved version of stable. Besides the fact that the same exact update was approved for beta, it's not a huge surprise that any update is getting flagged for manual review under the current circumstances. Google had yet another embarrassing scandal recently, so they've been enacting stricter policies across the board. If not, it gets flagged for manual review, which could take days, weeks, or even months. If it passes, it may be available in a couple hours. When updates are submitted, they go through an automated review process. Whatever actions they take, the review process is intentionally designed so that there is little to no recourse for developers. The reality of dealing with CWS is that we rarely know much more than you do. Read an excellent account of another developer's mishaps in dealing with extension stores, I am tempted to quote it here:
0 kommentar(er)
