<story><title> Apple Developer Indifference</title><url>http://blog.forecast.io/apple-developer-indifference/</url></story><parent_chain></parent_chain><comment><author>natch</author><text>&amp;gt;We shot off an email to Apple Technical Support — one of the two free emails Apple allows developers to send (after which they cost $99 for a 2-pack).&lt;p&gt;Wow, this statement is such drama.&lt;p&gt;There is no &amp;quot;allowance&amp;quot; for how many emails you can send to Apple. The Apple developer evangelist email is public and emails to it are not limited. The author is confusing emails and TSIs (Technical Support Incidents).&lt;p&gt;You can also call the developer support line, which picks up after a couple rings with a live human. And you can file bugs. And you can tweet to the developer evangelists, which may be the fastest, most effective way to get an urgent problem like this on their radar.&lt;p&gt;The two TSIs that are free with your developer account (and then cost after that, if you ever even use your first two) are for code-level support, meaning &amp;quot;how do I accomplish this with code.&amp;quot; This is clearly spelled out (see &lt;a href=&quot;https://developer.apple.com/support/technical/submit/&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.apple.com&amp;#x2F;support&amp;#x2F;technical&amp;#x2F;submit&amp;#x2F;&lt;/a&gt;).&lt;p&gt;They will get your question answered, if an answer is possible. Apple pulls out all the stops to get these resolved, and it&amp;#x27;s a huge misunderstanding of their purpose to use them for an outage report, and further to claim that you can only send two emails to Apple without paying.&lt;p&gt;Far from being indifferent, the Apple developer relations team is hitting it way out of the park. Yes, outages happen, and that&amp;#x27;s unfortunate. But there&amp;#x27;s no need to make something out of it that it&amp;#x27;s not.</text></comment>
<story><title> Apple Developer Indifference</title><url>http://blog.forecast.io/apple-developer-indifference/</url></story><parent_chain></parent_chain><comment><author>osipovas</author><text>A similar problem exists on the Android Platform. The Geocoding (forward and backward service) is non-reliable, sometimes requiring a device reboot. But, at least there is a public issue tracker!&lt;p&gt;&lt;a href=&quot;http://developer.android.com/reference/android/location/Geocoder.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;developer.android.com&amp;#x2F;reference&amp;#x2F;android&amp;#x2F;location&amp;#x2F;Geoc...&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https://code.google.com/p/android/issues/list?can=2&amp;amp;q=geocode&amp;amp;colspec=ID+Type+Status+Owner+Summary+Stars&amp;amp;cells=tiles&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;code.google.com&amp;#x2F;p&amp;#x2F;android&amp;#x2F;issues&amp;#x2F;list?can=2&amp;amp;q=geocod...&lt;/a&gt;</text></comment>