• Replies 25 replies
  • Subscribers 20 subscribers
  • Views 1638 views
  • Users 0 members are here
Options
Related

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

sososo
3 months ago

Hello, I'm having trouble uploading a beta connect iq application to Connect IQ Store since July 26th.

I cannot upload my app.

Am I the only one having this server connection error right now?

Is garmin server is on development or update process?

If it is, when can I upload my app?

Of course, my internet works well and I didn't miss any required inputs.

I tried at my work and my home. In both cases, I couldn't succed.

I also tried to check the developer dashboard if my app is already in the status of "pending".

But the account i'm trying to uplaod the app is new account. So, I cannot access the developer dashboard yet.

(I need to upload the first app to get into the developer dashboard.)

What can I do to solve this problem?

Thank you for reading my question.

  • 3 months ago in reply to flocsy🤠

    As I wrote, I tried several different watchfaces. I even made a super basic one with just the time to test if it had anything to do with the size or complexity, but all of them fail.
    Attaching works fine, I get the green box saying it's verified etc.

    I made two watchfaces earlier the same way for the same devices and they uploaded without issues.
    Could I maybe send one of them to someone to test/check?

  • 3 months ago in reply to 6973276

    Send it (the IQ file) to [email protected] .

    BTW the way you tried the different watchfaces was that you uploaded them to the same app in the store (with the same appId?) Or each of them to their own app (separate appIds)?

  • 3 months ago in reply to flocsy🤠

    I started from scratch each time. So with seperate appIds. I tried both as beta and normal.
    I've tried it several times each day since saturday evening. I figured it could've just been a temporary problem with the server so I waited a bit before reaching out.

    Thank you, I'll send it to the email.

  • 3 months ago in reply to 6973276

    Can you try this: upload one of the apps that does work, but change it's appId to the one that doesn't work and upload it into the app that doesn't work? If it won't work either then the problem is in the meta data (description, etc)

  • 3 months ago in reply to flocsy🤠

    I'm not sure what you mean by 'upload it into the app that doesn't work'
    These are new submissions, not updates to existing apps.

  • 3 months ago in reply to flocsy🤠

    I have found the problem; it was in the pictures weirdly enough.
    They were JPG's made in Photoshop, they have the correct dimensions and size and I could select them no problem but when trying to submit it would give me this error.
    I found this out while I was trying a bunch of different things, the successful test was when I selected the iq file of the new app that I couldn't upload, used the same descriptions etc but I used the pictures I had used for the earlier apps that did get added without problem, and suddenly it works.

    So I opened the pictures I made for the apps that kept failing in paint and saved them as a copy to get rid of any Photoshop metadata and now it uploads no problem.

    This may be interesting for devs as well as users who may stumble upon this problem in the future.

    tldr: something in the metadata of the pictures uploaded was causing this.

  • 3 months ago in reply to 6973276

    This is exactly why I recommended to upload one of the "good" apps into the "bad" app, to check if the problem is in the IQ file or in the meta data.

  • 3 months ago in reply to flocsy🤠

    yes thank you for the suggestion, it set me on the right path. Any idea why or what image metadata could trigger this error?

  • 3 months ago in reply to 6973276

    "knowing" Garmin, I wouldn't be surprised if some non ASCII text in the metadata could cause it.

  • 2 months ago in reply to 6973276

    Hello. I'm tried exaclty this but no lucky, I'm still getting the same error. It's seems like the bug comes from other side and I have no clue. My app is correclty deployed on my watch, all work fine. Help please,

    Thanks in advance