Automated security scan rejects app with identical generic message across 4 substantially different binaries

App: ALLCALENDAR - Calendar, Events & Reminders

App ID: b87620ff-a148-4859-8287-1c946b2ba234

My app was pulled by an automated scan ("An automated scan identified a security threat...") with no detail on the actual finding, and was removed from the store the same day, after an update submission. Since then I've resubmitted 4 times, each with a substantially different binary, specifically targeting things that could plausibly look risky to an automated scanner:

1) Removed the entire calendar-sync (ICS) feature and its network code - zero Communications.makeWebRequest calls related to it, feature stripped from settings too.

2) Removed a settings field that let the destination server address be overridden (an "arbitrary outgoing request target" pattern).

3) Removed a set of bare domain strings (no scheme prefix) that were present as a client-side allowlist.

4) Restored/varied the above between attempts.

All 4 submissions were rejected with the exact same templated email, no additional detail in either the email or the developer dashboard.

I've read a similar report here: "New listing inherits state from a deleted one - every upload rejected by the automated security scan" - in that case the cause turned out to be content (a bare-domain string), which I've now also removed, with no change in outcome for my listing.

Given the rejection appears insensitive to meaningfully different binary content, could someone from the Connect IQ team check whether this specific listing/App ID has a stuck or inherited review flag independent of the uploaded package? Happy to provide any binary/diff needed. This has kept a paid, previously-live app (100+ installs, 4.3 stars / 12 reviews) off the store since today.

Also emailed [email protected] but wanted to raise it here too in case someone can take a quicker look. Thanks!

  • Unfortunately for me I don’t have this device, so cannot just remove it to magically solve this mess for me.

  • Unfortunately this is still an issue for me Disappointed

  • I managed to make some progress.

    Using 7-Zip, I started testing the IQ file archives:
    1. right-click
    2. Show more options
    3. 7-Zip
    4. Test Archive

    I found that some older archives that I had stored on a NAS appeared corrupted for whatever reason (Multiple Data errors listed).

    I exported a new version directly to my desktop and tested it with a result of "There are no errors".

    I uploaded this version to the store, Connect IQ app found the update, queued it for install, and then said it was done. At this point, it still wasn't right. I followed hard refresh methods listed by others (which I also tried with previous versions with no success); this time it appears to have worked!

    Hard refresh method:
    1. Uninstall watch face from watch via Connect IQ app
    2. Clear Connect IQ App storage and Cache using phone (Settings -> Apps -> Connect IQ -> Storage and cache -> Clear storage + Clear cache)
    3. Restart the watch
    4. Re-sync the watch
    5. Install watch face via Connect IQ app (after signing in again due to cache clear)
    6. Success!


    I don't know why previous binaries were getting corrupted (Random strings of zeros in the middle of the binaries) whether this was the SDK doing it, or my storage method of the files, this is unknown, however happy to make progress.

  • Is this related to the security scanner issue?

    Have you received a Garmin email saying your submission was rejected by the security scanner?

  • The signing error could be the result of building the IQ file with an old SDK.  Not sure what the min is today (it was 7.x at one time), but I've been using 9.2 since it came out

  • Ok, I also found invalid devices and now all is fine after having them removed.
    Mine was the approachs70 and approachs70s.

    Hard lesson learnt:

    Regularly delete the SDK devices and redownload them so you always have a fresh cache of Garmin CIQ supported devices.

    Once I did this and compiled, I got compiler errors pointing out the invalid devices.

    This was a painful 2-3 weeks Smiley

  • I had a single rejection email for one version. And a bunch of the others went through but the binary on the store page never updated even though the store page did.