Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[Dianne Hackborn]

On Thu, Apr 1, 2010 at 11:56 AM, mike  wrote:

> On 04/01/2010 11:33 AM, Dianne Hackborn wrote:
>
>> "Be careful" means to test and run the app on the oldest version of the
>> platform you support to make sure it works.
>
> "Works" is the key word here. I'm guessing that "works" doesn't mean
> "the app started!". I assume that this means in reality full regression
> testing against every sdk.


My personal bar would be to fully test on the lowest version you support and
the current highest version of the platform.  Each platform between is a
superset of the next, so that will cover you for 99% of issues there may be.

To be a little more paranoid, do a spot check on the other intermediate
platform versions.

-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[~ TreKing]

On Thu, Apr 1, 2010 at 3:46 PM, Krishna Achanta
wrote:

> No it did not cause any problems on either the device[htc hero] or the
> emulator.
>

OK, so there you go ...


> I am asking because this part of the code may come into picture when the
> app is being downloaded from the market and i am not sure if that causes any
> problems.
>

No part of your code comes "into picture when the app is being downloaded" -
it only comes into the picture when the user runs it - which you've
apparently tested. So I really don't understand what you're worried about.

-
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[Krishna Achanta]

No it did not cause any problems on either the device[htc hero] or the
emulator.
I am asking because this part of the code may come into picture when the app
is being downloaded from the market and i am not sure if that causes any
problems.

On Thu, Apr 1, 2010 at 2:33 PM, ~ TreKing  wrote:

> On Thu, Apr 1, 2010 at 2:54 PM, Achanta  wrote:
>
>> I have added the jar and this code to my manifest but I am not sure if
>> this will cause any problems after releasing it into market.
>>
>
> Did this cause any problems on an emulator or device running 1.5?
>
>
>
> -
> TreKing - Chicago transit tracking app for Android-powered devices
> http://sites.google.com/site/rezmobileapps/treking
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[~ TreKing]

On Thu, Apr 1, 2010 at 2:54 PM, Achanta  wrote:

> I have added the jar and this code to my manifest but I am not sure if
> this will cause any problems after releasing it into market.
>

Did this cause any problems on an emulator or device running 1.5?

-
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.

[android-developers] Re: Can we release an updated version of app with lower min sdk?

[Achanta]

Its regarding the same issue but also related to analytics tracking.

So I analytics referrals work for android 1.6 and higher[from the
documentation]. So will this part cause any issues on 1.5.
  

  

  
I have added the jar and this code to my manifest but I am not sure if
this will cause any problems after releasing it into market.



On Apr 1, 1:10 pm, Achanta  wrote:
> Thank you all for the replies.
>
> I did test my app on a device working on 1.5 and it seems to be
> working[so far]. Will do more testing though.
>
> I was also searching for the blog post that Dianne was talking about
> but could not find it. Can someone post a link for that blogpost.
>
> Thank you.
>
> On Apr 1, 12:56 pm, mike  wrote:
>
> > On 04/01/2010 11:33 AM, Dianne Hackborn wrote:
>
> > > "Be careful" means to test and run the app on the oldest version of
> > > the platform you support to make sure it works.
>
> > "Works" is the key word here. I'm guessing that "works" doesn't mean
> > "the app started!". I assume that this means in reality full regression
> > testing against every sdk.
>
> > > Just doing automated tests to make sure you are not calling any older
> > > APIs is not a guarantee you will work.
>
> > No, sorry I didn't mean to imply it would. I was thinking more of a profiler
> > that highlighted potentially unsafe areas so that you can check them to
> > make certain that they're properly protected. What I'm most concerned
> > about is inadvertent introduction of later sdk calls. Sort of an SDK lint.
>
> > > In addition, it is typical for an application to take advantage of
> > > Java class loading to be able to use newer APIs if they are available
> > > (see for example my blog post on the new service APIs), and I don't
> > > see any way an automated tool could accurately determine whether that
> > > code is safe on an older platform.
>
> > > You just need to make sure you test your app in the key environments
> > > it will run.
>
> > Full regression testing is really onerous. The problem here is that it's
> > really really easy to fall into the pit trap here that you find out too late
> > (ie, in the field). And the problem is only going to get worse and worse
> > as time goes on.
>
> > I'll look for your article.
>
> > Mike
>
> > > On Thu, Apr 1, 2010 at 11:05 AM, mike  > > > wrote:
>
> > >     On 04/01/2010 10:53 AM, ~ TreKing wrote:
>
> > >         On Thu, Apr 1, 2010 at 11:51 AM, Achanta
> > >         mailto:krishna.acha...@gmail.com>
> > >          > >         >> wrote:
>
> > >            Still looking for someone to confirm it that it does not cause
> > >            any problems.
>
> > >         Um ... didn't Michael just do that?
> > >         There is no specific problem with what you're doing, except of
> > >         course properly testing all supported versions and being
> > >         careful if / how you use APIs that did not exist on 1.5.
>
> > >     Here's the question I have: define "be careful". If "be careful" means
> > >     inspecting every class/method call you make against SDK level, I think
> > >     you're setting yourself up for failure, as it's extremely easy to
> > >     miss that,
> > >     and the only time you find it is at run time, which for a seldom
> > >     run piece
> > >     of code could be pretty elusive.
>
> > >     It's would be a lot better to "be careful" by having some tool --
> > >     maybe in
> > >     the android dev tool chain or the eclipse plugin -- that
> > >     "carefully" goes
> > >     through your code looking for method/classes that are below the
> > >     current
> > >     SDK level. I'm sure there are even better ways to "be careful".
>
> > >     But as it right now, "be careful" is just a big smelly hack.
>
> > >     Mike
>
> > >     --
> > >     You received this message because you are subscribed to the Google
> > >     Groups "Android Developers" group.
> > >     To post to this group, send email to
> > >     android-developers@googlegroups.com
> > >     
> > >     To unsubscribe from this group, send email to
> > >     android-developers+unsubscr...@googlegroups.com
> > >     
> > >     For more options, visit this group at
> > >    http://groups.google.com/group/android-developers?hl=en
>
> > >     To unsubscribe, reply using "remove me" as the subject.
>
> > > --
> > > Dianne Hackborn
> > > Android framework engineer
> > > hack...@android.com 
>
> > > Note: please don't send private questions to me, as I don't have time
> > > to provide private support, and so won't reply to such e-mails.  All
> > > such questions should be posted on public forums, where I and others
> > > can see and answer them.
>
> > > --
> > > You received this message because you are subscribed to the

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[~ TreKing]

On Thu, Apr 1, 2010 at 2:10 PM, Achanta  wrote:

>  was also searching for the blog post that Dianne was talking about
> but could not find it. Can someone post a link for that blogpost.
>

http://android-developers.blogspot.com/2010/02/service-api-changes-starting-with.html

-
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.

[android-developers] Re: Can we release an updated version of app with lower min sdk?

[Achanta]

Thank you all for the replies.

I did test my app on a device working on 1.5 and it seems to be
working[so far]. Will do more testing though.

I was also searching for the blog post that Dianne was talking about
but could not find it. Can someone post a link for that blogpost.

Thank you.

On Apr 1, 12:56 pm, mike  wrote:
> On 04/01/2010 11:33 AM, Dianne Hackborn wrote:
>
> > "Be careful" means to test and run the app on the oldest version of
> > the platform you support to make sure it works.
>
> "Works" is the key word here. I'm guessing that "works" doesn't mean
> "the app started!". I assume that this means in reality full regression
> testing against every sdk.
>
> > Just doing automated tests to make sure you are not calling any older
> > APIs is not a guarantee you will work.
>
> No, sorry I didn't mean to imply it would. I was thinking more of a profiler
> that highlighted potentially unsafe areas so that you can check them to
> make certain that they're properly protected. What I'm most concerned
> about is inadvertent introduction of later sdk calls. Sort of an SDK lint.
>
>
>
> > In addition, it is typical for an application to take advantage of
> > Java class loading to be able to use newer APIs if they are available
> > (see for example my blog post on the new service APIs), and I don't
> > see any way an automated tool could accurately determine whether that
> > code is safe on an older platform.
>
> > You just need to make sure you test your app in the key environments
> > it will run.
>
> Full regression testing is really onerous. The problem here is that it's
> really really easy to fall into the pit trap here that you find out too late
> (ie, in the field). And the problem is only going to get worse and worse
> as time goes on.
>
> I'll look for your article.
>
> Mike
>
>
>
> > On Thu, Apr 1, 2010 at 11:05 AM, mike  > > wrote:
>
> >     On 04/01/2010 10:53 AM, ~ TreKing wrote:
>
> >         On Thu, Apr 1, 2010 at 11:51 AM, Achanta
> >         mailto:krishna.acha...@gmail.com>
> >          >         >> wrote:
>
> >            Still looking for someone to confirm it that it does not cause
> >            any problems.
>
> >         Um ... didn't Michael just do that?
> >         There is no specific problem with what you're doing, except of
> >         course properly testing all supported versions and being
> >         careful if / how you use APIs that did not exist on 1.5.
>
> >     Here's the question I have: define "be careful". If "be careful" means
> >     inspecting every class/method call you make against SDK level, I think
> >     you're setting yourself up for failure, as it's extremely easy to
> >     miss that,
> >     and the only time you find it is at run time, which for a seldom
> >     run piece
> >     of code could be pretty elusive.
>
> >     It's would be a lot better to "be careful" by having some tool --
> >     maybe in
> >     the android dev tool chain or the eclipse plugin -- that
> >     "carefully" goes
> >     through your code looking for method/classes that are below the
> >     current
> >     SDK level. I'm sure there are even better ways to "be careful".
>
> >     But as it right now, "be careful" is just a big smelly hack.
>
> >     Mike
>
> >     --
> >     You received this message because you are subscribed to the Google
> >     Groups "Android Developers" group.
> >     To post to this group, send email to
> >     android-developers@googlegroups.com
> >     
> >     To unsubscribe from this group, send email to
> >     android-developers+unsubscr...@googlegroups.com
> >     
> >     For more options, visit this group at
> >    http://groups.google.com/group/android-developers?hl=en
>
> >     To unsubscribe, reply using "remove me" as the subject.
>
> > --
> > Dianne Hackborn
> > Android framework engineer
> > hack...@android.com 
>
> > Note: please don't send private questions to me, as I don't have time
> > to provide private support, and so won't reply to such e-mails.  All
> > such questions should be posted on public forums, where I and others
> > can see and answer them.
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" group.
> > To post to this group, send email to android-developers@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@goog

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[mike]

On 04/01/2010 11:33 AM, Dianne Hackborn wrote:
"Be careful" means to test and run the app on the oldest version of 
the platform you support to make sure it works.


"Works" is the key word here. I'm guessing that "works" doesn't mean
"the app started!". I assume that this means in reality full regression
testing against every sdk.

Just doing automated tests to make sure you are not calling any older 
APIs is not a guarantee you will work.


No, sorry I didn't mean to imply it would. I was thinking more of a profiler
that highlighted potentially unsafe areas so that you can check them to
make certain that they're properly protected. What I'm most concerned
about is inadvertent introduction of later sdk calls. Sort of an SDK lint.



In addition, it is typical for an application to take advantage of 
Java class loading to be able to use newer APIs if they are available 
(see for example my blog post on the new service APIs), and I don't 
see any way an automated tool could accurately determine whether that 
code is safe on an older platform.


You just need to make sure you test your app in the key environments 
it will run.


Full regression testing is really onerous. The problem here is that it's
really really easy to fall into the pit trap here that you find out too late
(ie, in the field). And the problem is only going to get worse and worse
as time goes on.

I'll look for your article.

Mike



On Thu, Apr 1, 2010 at 11:05 AM, mike > wrote:


On 04/01/2010 10:53 AM, ~ TreKing wrote:

On Thu, Apr 1, 2010 at 11:51 AM, Achanta
mailto:krishna.acha...@gmail.com>
>> wrote:

   Still looking for someone to confirm it that it does not cause
   any problems.


Um ... didn't Michael just do that?
There is no specific problem with what you're doing, except of
course properly testing all supported versions and being
careful if / how you use APIs that did not exist on 1.5.


Here's the question I have: define "be careful". If "be careful" means
inspecting every class/method call you make against SDK level, I think
you're setting yourself up for failure, as it's extremely easy to
miss that,
and the only time you find it is at run time, which for a seldom
run piece
of code could be pretty elusive.

It's would be a lot better to "be careful" by having some tool --
maybe in
the android dev tool chain or the eclipse plugin -- that
"carefully" goes
through your code looking for method/classes that are below the
current
SDK level. I'm sure there are even better ways to "be careful".

But as it right now, "be careful" is just a big smelly hack.

Mike


-- 
You received this message because you are subscribed to the Google

Groups "Android Developers" group.
To post to this group, send email to
android-developers@googlegroups.com

To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.




--
Dianne Hackborn
Android framework engineer
hack...@android.com 

Note: please don't send private questions to me, as I don't have time 
to provide private support, and so won't reply to such e-mails.  All 
such questions should be posted on public forums, where I and others 
can see and answer them.


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[Dianne Hackborn]

"Be careful" means to test and run the app on the oldest version of the
platform you support to make sure it works.

Just doing automated tests to make sure you are not calling any older APIs
is not a guarantee you will work.

In addition, it is typical for an application to take advantage of Java
class loading to be able to use newer APIs if they are available (see for
example my blog post on the new service APIs), and I don't see any way an
automated tool could accurately determine whether that code is safe on an
older platform.

You just need to make sure you test your app in the key environments it will
run.

On Thu, Apr 1, 2010 at 11:05 AM, mike  wrote:

> On 04/01/2010 10:53 AM, ~ TreKing wrote:
>
>  On Thu, Apr 1, 2010 at 11:51 AM, Achanta > krishna.acha...@gmail.com>> wrote:
>>
>>Still looking for someone to confirm it that it does not cause
>>any problems.
>>
>>
>> Um ... didn't Michael just do that?
>> There is no specific problem with what you're doing, except of course
>> properly testing all supported versions and being careful if / how you use
>> APIs that did not exist on 1.5.
>>
>
> Here's the question I have: define "be careful". If "be careful" means
> inspecting every class/method call you make against SDK level, I think
> you're setting yourself up for failure, as it's extremely easy to miss
> that,
> and the only time you find it is at run time, which for a seldom run piece
> of code could be pretty elusive.
>
> It's would be a lot better to "be careful" by having some tool -- maybe in
> the android dev tool chain or the eclipse plugin -- that "carefully" goes
> through your code looking for method/classes that are below the current
> SDK level. I'm sure there are even better ways to "be careful".
>
> But as it right now, "be careful" is just a big smelly hack.
>
> Mike
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>
> To unsubscribe, reply using "remove me" as the subject.
>



-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[mike]

On 04/01/2010 10:53 AM, ~ TreKing wrote:
On Thu, Apr 1, 2010 at 11:51 AM, Achanta > wrote:


Still looking for someone to confirm it that it does not cause
any problems.


Um ... didn't Michael just do that?
There is no specific problem with what you're doing, except of course 
properly testing all supported versions and being careful if / how you 
use APIs that did not exist on 1.5.


Here's the question I have: define "be careful". If "be careful" means
inspecting every class/method call you make against SDK level, I think
you're setting yourself up for failure, as it's extremely easy to miss that,
and the only time you find it is at run time, which for a seldom run piece
of code could be pretty elusive.

It's would be a lot better to "be careful" by having some tool -- maybe in
the android dev tool chain or the eclipse plugin -- that "carefully" goes
through your code looking for method/classes that are below the current
SDK level. I'm sure there are even better ways to "be careful".

But as it right now, "be careful" is just a big smelly hack.

Mike

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.

Re: [android-developers] Re: Can we release an updated version of app with lower min sdk?

[~ TreKing]

On Thu, Apr 1, 2010 at 11:51 AM, Achanta  wrote:

> Still looking for someone to confirm it that it does not cause
> any problems.
>

Um ... didn't Michael just do that?
There is no specific problem with what you're doing, except of course
properly testing all supported versions and being careful if / how you use
APIs that did not exist on 1.5.

-
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.

[android-developers] Re: Can we release an updated version of app with lower min sdk?

[Achanta]

thank you Michael.

Still looking for someone to confirm it that it does not cause any
problems.

On Apr 1, 10:39 am, Michael Rueger  wrote:
> On 4/1/2010 6:36 PM, Achanta wrote:
>
> > We have an app thats running on 1.6 and higher but we want it to be
> > able to run on 1.5 also. So I tested the app with 1.5 and everything
> > works fine. So if I want to release this app can I release it as an
> > update for my older app with just changing
>
> >        to
> >      ?
>
> > Will there be any problems if I do so?
>
> We did that with our app it seems to work fine.
>
> Michael

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

To unsubscribe, reply using "remove me" as the subject.