Submitting to Apple's App Store pt.3: Apple Guidelines violated (Garmin Connect req)

Former Member
Former Member
Hello,

sorry for being boring with these issues, but I just keep running into them. I've already complained for various difficulties while developing and publishing a companion app for iOS. Here's the latest of these issues: I have an app that is published and available in the App Store, and it turns out it has a stupid bug. I made a bug-fix, it literally means changing a single line of code. But when I try to submit that version to the App Store, I am being told that my app violates Apple's App Store guidelines, because my app requires the Garmin Connect app to be installed.

I ask for Garmin's help on this matter, because requiring the Garmin Connect app to be installed is according to Garmin's own companion app development guidelines.

And that is very logical, of course, the problem is how do I convince the lads at Apple to understand this? I've appealed to the app review board, I've spoken with their representative on the phone, but they keep insisting that Apple's guidelines were clear at stating that an app must not require another app to be installed in order to function.
  • I don't have a great answer for you right at this moment, but I have the email you sent regarding this and I will forward it on to the illustrious AlphaMonkey since he's already been working with the another developer that contact us about the same issue. This hasn't been a problem with Apple until just recently, and I'm not sure what's caused them to pivot on this issue.
  • Former Member
    Former Member
    Hi Brandon,

    thank you very much! I was also surprised, since I already published the same app. I have a similar application for the Pebble, which of course, functions in the same manner. And all Pebble / Garmin related iOS apps do the same. Speaking on the phone I even asked if this was an attempt to block a competitive product, since they have the Apple Watch now. Of course they wouldn't admit it, even if it were the case, but they didn't seem to care about this issue. They're treating us as if we were the manufacturers of the watch and could implement our apps any way we wanted, in compliance with Apple's guidelines.
  • Former Member
    Former Member
    Any progress on this issue, after more than a month?
  • I don't have any updates right now, unfortunately, but I've asked to see if there's been any headway.
  • There isn't much we're able to do in this case. This is similar in nature to the issue discussed over on this thread:

    https://forums.garmin.com/showthread.php?370322-Submitting-to-Apple-s-App-Store-pt-2-Hardware-needed

    In that case, we weren't involved, but developers found a way to work with Apple.
  • And that is very logical, of course, the problem is how do I convince the lads at Apple to understand this?


    Let's say you are able to convince the responsible Apple staff to understand the logic. Does that mean, under any framework or in any doctrine, that Apple must then either vary its policies, or make exceptions or grant exemptions, in order to accommodate what you want, however “logical” or (I assume you're implying) reasonable you think the desired outcome is? Could Apple not simply take the position of, “We get it, but that's just too bad for you. Go talk to Garmin and get them to change its guidelines or exempt you, and come back when you win. No, that doesn't mean we'll work with Garmin on a compromise solution or special agreement; all the changes need happen on your and/or Garmin's end”?
  • Former Member
    Former Member
    So the idea of creating Garmin companion apps for iOS is effectively dead?
  • Former Member
    Former Member
    So the idea of creating Garmin companion apps for iOS is effectively dead?


    That is exactly what it means. That's why I was hoping that someone from Garmin would be able to help me out. Otherwise, they just need to remove the iOS companion app development guidelines and tools from their site, as it won't be fair to give false guidelines to the developers.
  • Former Member
    Former Member
    @ASmugDill two things:

    1. In this case Garmin's developer guidelines are incompatible with Apple's policies and thus need to be removed or reworked to be compatible.

    2. There's a huge factor of randomness when it comes to Apple App Review teams and policies. What may be allowed by one reviewer, could easily be blocked by someone else. That's why I managed to publish my app, but I'm not allowed to update it.
  • Former Member
    Former Member
    That is exactly what it means. That's why I was hoping that someone from Garmin would be able to help me out. Otherwise, they just need to remove the iOS companion app development guidelines and tools from their site, as it won't be fair to give false guidelines to the developers.


    RIP Garmin iOS companion app developing.