title: On-demand resources uploading failure
body: <p>Recently I have faced with problem of uploading on demand resources. I am using Xcode 9.0 for uploading app to AppStore and every uploading finishes successfully. But looking at iTunes Connect build details I can see, that on-demand resources are enabled, but there are 0 assets packs for this build.</p>
  
  <p>There is one more interesting moment in this problem. Build number 3 of my app also was uploaded with on-demand resources and everything works great with that build. But builds number 4 and 5 doesn't have assets packs included. I reviewed changes in application - there are no changes connected with on-demand resources at all.  </p>
  
  <p>In Xcode->Build Settings -> Assets ->Embed Asset Packs in Product Bundle is set to No. Also, size of one asset pack is around 5MB, total size of all packs around 150MB. </p>
  
  <p>Maybe, someone had this problem too? Thanks.</p>
  
  <p><strong>UPDATE</strong>
  I have checked Product folder inside the Xcode archive - there are all 36 assets packs, but iTunes Connect still shows 0 packs.</p>
  
  <p><strong>UPDATE 2</strong>
  It seems, that it happened not once. Developers had <a href="https://stackoverflow.com/questions/38422752/on-demand-resources-0-asset-packs?rq=1">the same problem</a> one year ago. I think, we should report a bug to Apple.</p>
  
  <p><strong>UPDATE 3</strong>
  We tried to upload app with on-demand resources using Application Loader, but result was the same. </p>
  
  <p><strong>UPDATE 4</strong>
  We tried to revert code to version where everything works great with on-demand resources and upload the same binary with different version number to iTC, but result is the same.</p>
  
  <p><strong>UPDATE 5</strong> We received an answer from Apple Developer Technical Support (DTS)</p>
  
  <blockquote>
    <p>Thank you for contacting Apple Developer Technical Support (DTS). 
    Our engineers have reviewed your request and have determined that you are experiencing a known issue for which there is no known workaround at this time.</p>
  </blockquote>
  
  <p>I will post any updates here connected to this issue.</p>