Dashboard - Why Always - "Sorry, your message couldn’t be submitted because we’re having trouble communicating with our servers. Please try again later."

Nemiz 1 month ago

(None of the existing issues reported with this error are of help to me. Don't redirect)

Issue: I have tried uploading new apps and updating existing apps since before Christmas 2024, and every time I get the:

"Sorry, your message couldn’t be submitted because we’re having trouble communicating with our servers. Please try again later."

Every single time.

I refuse to believe the servers are that difficult to communicate with, so there must be some underlying problem that just isn't being reported correctly back.

I often get through to the "Step 2: Enter Details" page, leading me to believe, that the .iq file has been uploaded, but I never get further than that, so maybe not?

"Sorry, your message couldn’t be submitted because we’re having trouble communicating with our servers. Please try again later." appears every time, sometimes after a couple of seconds, sometimes after 10 seconds.

Note: My .iq files are between 20-40 MBs in size, which I guess could be the issue, but I have uploaded 40+ MB .iq files in the past.

I did sometimes have to try several times back then, before it succeeded, but this time it doesn't matter how many times I try.

It always fails.

Top Replies

All Replies

Dreed 28 days ago

When you get the error message select your Browser developer tools. Go to Network tab and check the red lines where POST the form. The return code 50X and in the preview you get the problem Enum name in JSON. (because its a name well describe what is the problem)

flocsy🤠 28 days ago in reply to Dreed

If the client already gets this information then Garmin should just display that in the visible error message.

Dreed 28 days ago in reply to flocsy🤠

In an optimal world. But in garmin form all error displayed this one text

Nemiz 28 days ago in reply to Dreed

Excellent suggestion. There was indeed a more detailed error description, which pointed me in the right direction. Turns out I had checked of a couple of "preview" devices in my supported devices list. Thanks for the help :)

Nemiz 28 days ago in reply to flocsy🤠

I completely agree. If they had just shown me that underlying error message, I would have figured out the problem weeks ago :/

Dreed 28 days ago in reply to Nemiz

My pleasure! Good you find the problem!

jim_m_58 28 days ago in reply to Nemiz

If I recall, there used to be a message about "invalid part number" when you tried to upload an iq file with a "preview" (fake) device, but it seems they went back to a generic message.

What to learn here is that you NEVER want to have a "preview"/placeholder device when you build an iq file for the store.

Just today, there is a new preview device. The "System 8 Preview Device". Do not try to build an iq file for the store with it!

flocsy🤠 28 days ago in reply to jim_m_58

jim_m_58 said:
What to learn here is that you NEVER want to have a "preview"/placeholder device when you build an iq

Yes, and maybe that could be ensured by the compiler!

jim_m_58 28 days ago in reply to flocsy🤠

The compiler doesn't know what's a fake device, and in fact the whole purpose of them is so you can test with them in the sim.

The store knows to reject them, and the dev needs to know to exclude them from the IQ file.

flocsy🤠 28 days ago in reply to jim_m_58

I'm talking about building an IQ file: the compiler should either just skip the preview devices or at least give a warning that I forgot to remove them from the manifest. There's no point adding them to the iq file, because I can't upload them to the store, so...