• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 108 views
  • Users 0 members are here
Options
Related

What is the maximum .iq file size for Connect IQ Store uploads

masaclaw

Hello,

I couldn't find this documented anywhere or answered specifically in this forum. I'm trying to upload my app to the Connect IQ Store and encountering upload failures when the .iq file exceeds a certain size. Through trial and error, I've found:

  • 72MB - uploads successfully
  • 89MB - fails with a 520 error (server returns "Maintenance" page, page displays a generic message "Sorry, your message couldn’t be submitted because we’re having trouble communicating with our servers. Please try again later.")

The error occurs during the /api/ciq-developerservices/iqFiles/validate API call - it times out after ~48 seconds and returns a Cloudflare 520 error. I've successfully uploaded a 102MB file for a different app in the past, so I'm confused about the actual limit.

Questions:

  1. Is there a documented maximum file size for .iq uploads?
  2. Is there a maximum number of device targets per submission?
  3. Are there any other factors that could cause validation to fail/timeout for larger files?

SDK version: 8.4.0
Build command: monkeybrains.jar -e -r -w

Thanks for any help!

  • 0

    Update: I found a workaround that others might find useful.

    The workaround:

    1. Submit the initial app version with only a few devices (keeping the .iq file small)
    1. Once published, go back to the developer dashboard and upload a new version with the full device list
    1. The upload will appear to fail with the same 520/timeout error
    1. However, after ~10 minutes the app updates to show the new version - it seems the validation continues processing in the background despite the error

    This worked for me with a 132MB iq file. 

    So it appears the upload/validation does eventually complete, but the web interface times out before it finishes for larger files. The backend continues processing successfully.This isn't ideal UX but it does work for getting larger apps published. Hopefully this helps anyone else hitting the same issue until there's an official fix.