App submission stuck in "pending" for ~3 weeks

Hi, my Connect IQ data field "Pacevine — Trail & Ultra Race Pacing" (app ID: 077c3175-c0c6-4f7d-b006-a2ef65ead3aa) has been in "pending" review for about three weeks with no status change. Could someone check whether it's flagged for changes on my side or just stuck in the review queue? Happy to provide any additional info. Thanks!

  • Unfortunately, not much will happen. I had the same problem with an app and after some searching, I found the cause. You have a manifest where you specify which watches are compatible with your app, and that's where the problem lies. Their automation probably indicates that there are issues with at least one of the watches you've listed, but that doesn't mean you'll be notified. Here's how I solved it: I own several Garmin watches, and as a first step, I physically tested the app on these watches (Fenix ​​8, Forerunner 255m). I learned that the emulator ran smoothly, but there were problems on the watches themselves. I fixed that, added only those two watches to the manifest, and submitted it to the store: voila – it went through. After that, I categorized the manifest step by step into product families and discovered that, in my case, the older Instinct models were causing the problems. I hope this helps you.

  • that sounds strange. Are you sure you added back all other devices except the old instincts? 

  • In my special case there were not only the old instinct watches but all watches leaking enough video memory.  It really depends on what you are building. 

  • But that ALONE is still strange. I would've think that Garmin don't care much whether your app runs or crashes on the devices in your manifest, but from what you wrote I am trying to think that they have some check, and if an app crashes on startup then they block it (let's assume for now). But if that's the case then the issue here, that would probably need a bug report is that running the same app in the simulator does work. And if the "leak" is something that happens after a while, then it's even harder to believe that Garmin detect it and then silently block the app release.