Acknowledged
CIQQA-4716

First app upload: “Status: Verified” but “Signature check failed” — SDK 9.2.0

Hello Garmin Connect IQ team,

I am uploading Challenge 0.12.4 to the Connect IQ Store for the first time.

At Step 2, the green App File panel shows both:
Status: Verified
Signature check failed.

Environment:
- Windows, Connect IQ SDK 9.2.0
- Exported using monkeyc -e with the existing developer signing key
- Build successful for all five devices
- Manifest AppID: 980a27cc50e349408ef17f169123efa4
- Devices: D2 Air X15, Venu 3, Venu 3S, Venu 4 41mm and 45mm

Local verification:
- Archive integrity check passed.
- The manifest SHA256 signature verifies using the embedded public key.
- Both SHA1 and SHA256 signatures for all five executable files verify locally.
- The package has not been repacked, and the signing key and AppID have not been changed.

Expected: Valid signatures should be accepted.
Actual: The upload page reports “Signature check failed” without further details.

I have not clicked the final Submit button. Can you clarify which signature check is failing, and whether this is a display issue or an export problem?

I can provide the IQ package if needed.

7998690
Parents

  • I ran into the same signature check error during my very first beta upload. Out of curiosity, I went ahead and clicked the final submit button anyway, and to my surprise, it actually uploaded successfully. After that, I tried updating the app, and this time the dashboard showed 'Signature: Verified' and everything worked perfectly. I even tried generating a new developer key earlier, but it made no difference—the issue seems strictly tied to the initial upload process itself.

Comment

  • I ran into the same signature check error during my very first beta upload. Out of curiosity, I went ahead and clicked the final submit button anyway, and to my surprise, it actually uploaded successfully. After that, I tried updating the app, and this time the dashboard showed 'Signature: Verified' and everything worked perfectly. I even tried generating a new developer key earlier, but it made no difference—the issue seems strictly tied to the initial upload process itself.

Children