title: Where do you file bugs for Android/iOS Google Products or Services (AppInvites, Maps, etc...)?
body: <p>I've recently found a bug on the Android SDK for AppInvites.</p>
  
  <p>I searched the web, looking for a bug tracker for AppInvites and couldn't find any.</p>
  
  <p>So I <a href="https://code.google.com/p/android/issues/detail?id=189782" rel="nofollow">posted</a> on the classic b.android.com receiving this response from a Googler:</p>
  
  <blockquote>
    <p>Sorry, this tracker is for issues with the Android OS only. Please use <a href="https://support.google.com/" rel="nofollow">https://support.google.com/</a> to obtain support for Google products or services.</p>
  </blockquote>
  
  <p>which was not useful at all. The support google page just list support pages for end users, not for developers, and there's nothing there that can work as a bug tracking tool for AppInvite.</p>
  
  <p>So I tried to <a href="https://groups.google.com/forum/#!topic/android-developers/WrL7cN-GqyA" rel="nofollow">post</a> in the Google Group android-developers@googlegroups.com, to just discover a while later that group has been <a href="https://groups.google.com/forum/#!topic/android-developers/EgCgsuQbfvA" rel="nofollow">discontinued by Google in favor of StackOverflow</a>. But since I can't do a bug report on a Google Product here I just ask for the right place to report a bug to Google.</p>
  
  <p>Example of Google Products or Services:</p>
  
  <ul>
  <li>Google Play Services Android/iOS SDK</li>
  <li><strong>Google AppInvites</strong> Android/iOS SDK</li>
  <li>Google Maps Android/iOS SDK</li>
  <li>Google Analytics  Android/iOS SDK</li>
  <li>etc...</li>
  </ul>
  
  <p>So, <strong>where do I file a bug to Google about one of its Android (or iOS) SDK / products for developers?</strong></p>
  
  <p>Edit: this question was closed because some people think this is off topic. It's not! This speaks about tools commonly used in development. Finding bug in SDK is part of programming. Filing bug on those instrument is either a good practice and sometimes the only option to have your bug fixed. For this reason I think this is on-topic.</p>