Signature Check failed after upgrading to SDK 7.x.x

I have a datafield that builds and sideloads successfully onto my Fenix 5S Plus with SDKs <= 6.4.2.

When I upgrade to any SDK 7.x.x version, the build is successful BUT sideload fails due to Signature check. I didn't change the developer key and I've also uninstalled older versions of the datafield from the IQ store.

I've seen a couple of comments that mentions this issue, but there's no discussion on it. Any help on this would be appreciated!

---
Error: 'Signature check failed on file: mydatafield'
Time: 2024-09-04T20:26:43Z
Part-Number: 006-B2900-00
Firmware-Version: '19.30'
Language-Code: eng
---

Top Replies

Kyle.ConnectIQ 2 months ago in reply to 1337273 +2 suggested

When you export an app for the store it builds a PRG targeting each device listed in the manifest file, so this won't be a problem. In the 7.0 SDK we optimized a few things to reduce the PRG size, but…
FlowState 2 months ago in reply to 1337273 +1

1337273 said:
We build the datafield for multiple watches (new and some old), so for testing, I typically don't specify the device.

Oh I was gonna say that with a recent firmware change, it doesn't seem…

All Replies

0 flocsy🤠 2 months ago

Yeah, it's something Garmin keeps silent about. It doesn't seem to have any effect besides being annoying and making devs freak out

0 Kyle.ConnectIQ 2 months ago

What device are you building the PRG for? This can happen if you build for a newer device but load the PRG on an older one.

0 flocsy🤠 2 months ago in reply to Kyle.ConnectIQ

No, it happens ever since SDK 7.x when we built a prg for a specific device that we have and we side load it on that specific device. I don't remember on which one it was but it's either fenix6 or fr965 or both.

0 jim_m_58 2 months ago in reply to flocsy🤠

Wasn't a version of the 3rd party optimizer extension that changed things in the prg post compile involved?

0 Kyle.ConnectIQ 2 months ago in reply to flocsy🤠

Does this still happen for these devices? There was a point if you built for these devices using a newer SDK, older SW wouldn't be able to run the app if you side loaded it. But this shouldn't be happening when building for the Fenix 5s Plus.

0 flocsy🤠 2 months ago in reply to jim_m_58

This happens even without the prettier monkey c optimizer

0 flocsy🤠 2 months ago in reply to Kyle.ConnectIQ

I'll try it later if it still happens, but it was only this warning. The app still worked.

Though it's obvious it still happens, that's what the OP is about...

0 Kyle.ConnectIQ 2 months ago in reply to flocsy🤠

Thanks for taking a look. The devices you're mentioning run a newer CIQ than the Fenix 5s Plus. I'm wanting to see if it's just a problem with just the Fenix 5 or if there's still more issues that need to be investigated.

0 1337273 2 months ago in reply to Kyle.ConnectIQ

We build the datafield for multiple watches (new and some old), so for testing, I typically don't specify the device.

After trying to build with specifying the device (i.e. monkeyc -d fenix5splus ... ), I can successfully sideload now! (AH, rookie mistake)

Thanks for your help!

0 1337273 2 months ago in reply to flocsy🤠

Since I'm trying to build for multiple devices, I wanted to double check if this only affects side loading? We're hoping to use SDK 7.x when releasing our next build onto the IQ store.