Unfortunately it is a bit of a mess. You have to install it for each user. And if you want to get properly rid of of your app you must uninstall it for each user account. I once had a stupid situation where I had to install a downgraded version of one of my apps for reproducing a bug. It was not enough to just uninstall the app for the one account I was testing on. I had to do it for all. It seems like the APK is shared, which is reasonable of course, given limited storage space.
However, I still think that the lack of a notification is worth a bug report. You have to explicitly activate USB debugging for your secondary account anyway, so it's not just a primary privilege of your main account. Not getting any kind of notification or error message made me waste 10 minutes trying to figure out what was going on. I even believed that the latest update bricked the USB debugging feature. On Thursday, February 21, 2013 7:58:10 PM UTC-6, Nikolay Elenkov wrote: > > On Fri, Feb 22, 2013 at 10:31 AM, Nikolay Elenkov > <[email protected] <javascript:>> wrote: > > On Fri, Feb 22, 2013 at 10:20 AM, Mark Murphy > > <[email protected]<javascript:>> > wrote: > >> On Thu, Feb 21, 2013 at 8:14 PM, Nikolay Elenkov > >> <[email protected] <javascript:>> wrote: > >>> This is most probably intentional -- whitelisting a host affects the > >>> whole system, > >>> and only the administrator (first) user should be able to do it. It is > the same > >>> with installing certificates, etc. You certainly wouldn't want anyone > that you > >>> lent the device to to change the system configuration and open up > potential > >>> security holes without you knowing about it. > >> > >> I agree, a secondary account shouldn't be able to make the change. > >> > >> However, *some* dialog should still appear, telling the person holding > >> the tablet "sorry, you must be on the primary account to activate USB > >> debugging". > > > > No, it should say: 'Go away, stop messing with MY tablet!' :) > > > > Seriously though, USB debugging should probably be switched off > > unconditionally when you change to a non-admin account. Thus > > the device will not even show up when connected. Or is this the > > current behaviour? (don't have a tablet right now) > > But then again, testing how your app behaves in a multiuser > environment becomes somewhat tricky. Is there a way to > 'activate' an app that is already on the device for a certain > user using the UI? Or you need to 'install' it again by downloading, > etc.? > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
