SDK 7.4 is bugged to export in production.

We've pulled the SDK and are looking into the issue. 

"The message could not be sent due to communication problems with our servers. Please try again later."
I get this error when I try to upload an app compiled with 7.4.0 (tried since 12 hours). No problems with the same app on 7.3.0

I see the same thing when I build an iq file with 7.4.0 and try to update the store.  As Kyle said they pulled 7.4,0, I'll just wait until they re-release it to try again and will stick with 7.3.1 until then.

For those of you who grabbed 7.4.0 in the brief few hours while it was live, how did you know a fresh version was available so soon after it was published?

Given all the issues with 7.3.1 (the well-known Storage.setValue bug), I've been refreshing the developers page constantly hoping for a new version.  But I'm wondering if there's a better way.

For me, I saw it was available when I ran the sdkmanager,  That's something I do maybe once every week or so to check for update to the device files.

If someone mentions a new SDK in this forum, I'll also download it right away

This is kind of an odd case where 7.4.0 was pulled so quickly

jim_m_58 said:

I do maybe once every week or so

Same!

Although I admit I've been checking almost daily recently because I'm so eager to publish updates that hopefully resolve the platform-level bugs. I was thrilled when I saw it on https://developer.garmin.com/connect-iq/overview/ but then confused why it wasn't in the SDK manager yet.  Fortunately, I saw this post right after that.

I was just surprised that you and TitanicTurtle had gotten it within that brief few hours. Wasn't sure if it was lucky timing or you had some other way you got notified about this stuff.

I'm subscribed to the developer update email newsletter, but I don't feel like I get a lot through that channel.

By any chance, if you still have the SDK locally, can you satisfy my curiosity by posting the changelog from the release notes?  I'm curious what's new/fixed with this one.

It was a coincidence in my case.
I've been checking the forums a lot lately to find out about recent bugs, and I saw this thread.
And since I'm about to release a new application, I gave 7.4.0 a try. (But in such cases I also regularly open the SDK Manager like Jim)

jim_m_58 Makes sense, didn't know what was meant by ‘pulled’ in this case.

Release Notes 7.4.0:

General Changes

    Add documentation about arrays in MSS classes.
    Fix an issue displaying bitmaps on monochrome devices.
    Various documentation fixes in the Programmer’s Guide.
    Update default launcher icons to be based on app type.

Simulator Changes

    Fix the Peak Stack Trace and Show Peak Memory buttons in the memory viewer being disabled.
    Fix unable to load a debug.xml file in the profiler on MacOS.
    Fix the Edge browser not being used on some Windows computers.
    Fix View.onUpdate() being called too many times during an animation.
    Fix several issues with WatchUi.Menu2.
    Fix weather observation time not saving correctly in the Set Weather dialog.
    Fix header images in WatchUi.Menu2 from being incorrectly scaled.
    Display a pop-up when calling bonded BLE functions which are not currently supported in the simulator.
    Match each device complication format for calendar event times.
    Better match the toast UX for each device.
    Change the keyboard shortcut for the Simulation menu to m in order to not conflict with the Settings menu shortcut.
    Prevent crash when closing the simulator through the MacOS dock.
    Update the message displayed in the Screen Burn-in Simulator window.
    Prevent crash on MacOS 12 and earlier when launching the simulator.

Compiler Changes

    Improve the unreachable code error with if statements.
    Add jungle and manifest files to the debug logs.
    Fix incorrect code generation for a WatchUi.Menu2 resource.
    Fix constant folding of float and long types to match API level behavior.
    Fix out of memory errors when compiling an app containing large resources.
    Fix incorrect symbol not found errors when calling functions on an enum value.
    Fix incorrect type checking error when using typedefs.

Thanks for sharing! I always find that the release notes tell a story about what the CIQ team considered most important to fix.

The simulator has been crashing regularly since the 6 -> 7 transition. My computer is MacOS > 12, so not sure if the fixes they cited will help, but here's to hoping.

The profiler/debugger has also been inoperable lately, so " Fix unable to load a debug.xml file in the profiler on MacOS" is a welcome sight.

I wonder if " Fix several issues with WatchUi.Menu2." will fix the issue where a momentum-scroll performs the scroll and then resets back to the initial position at the top of the menu.

I really wish there was an automated diff on the documentation changes.  I might look into some scripts/utils to generate that.  Does anyone already do this / have tips?

In the 9 years I've been doing CIQ, the number of times an SDK was released and then removed/pulled back, I can count on one hand.  Maybe just a couple fingers!

Garmin is likely scrambling right now to release a version with fixes, so I'd expect something soon.