I expect that almost if not all of the calendar-reading apps use the "undocumented" API that you are using. I see that the Pure Calendar Widget had the same problem which is a paid app. The guy who wrote that app has found a solution, so there is something that you can do, but I'm not sure what the solution is yet either.
On May 25, 9:32 am, andreas <[email protected]> wrote: > Well, since my app is free and I am not doing that as a business, I > will add a null check and open a window and tell the user the reason, > why he can't use the app on his brandnew froyo device. :-) > > On 25 Mai, 17:52, TreKing <[email protected]> wrote: > > > I highly doubt this since the Google Engineers are pretty adamant about > > people NOT using unpublished APIs. > > They're probably not going to help you continue to do so. Unfortunately this > > is the risk you take in doing so. > > > In the meantime, consider doing a null check on that line and giving the > > user an error message. It's better than outright crashing. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
