Hello, I have 100s if not 1000s of people at work needing this release to get millions of packages delivered everyday! I’m excited for them to get it to ensure all of the timely deliveries globally.
Name: AMZL Wins!
uuid: {cd5438df-2f5c-4e75-8792-2418a275061f}
Versions: 1.0.5.55, 1.0.6.0
Submissions: 3/14,3/27
I know it takes a while for the first review it’s just internally we need it distributed asap.
Why don’t you use an Enterprise policy or suggest they use the Nightly build to bypass the review process entirely until it’s approved officially and on the stable release?
Reducing those 132 warnings could also help with review speed as I can imagine, reviewer will need to check them, if that’s actually possible 
.
Hi @javenciu and apologies for the late reply, I am not sure how I missed your message.
Enterprise policy is a great way to ship updates way quicker to your users, and in your case, it’s highly recommended. However, even if you ship your add-on using the enterprise policy, it’s still subject to human review, and addressing the 132 warnings will help reviewers go through your add-on more quickly and possibly avoid human review in the first place.
If you need any help addressing those warnings, I am here to help!
