Dianne Hackborn wrote:
> The system doesn't cache anything about the contents of manifests across
> boots, so there is no way this can just not work.
My scenario does not involve boots, FWIW.
http://code.google.com/p/android/issues/detail?id=2376
> One thing that can happen is that when you mak
The system doesn't cache anything about the contents of manifests across
boots, so there is no way this can just not work.
One thing that can happen is that when you make a shortcut on the home
screen, this does of course reference the explicit component the shortcut is
for. So if the application
Ward Willats wrote:
> Well, that's a relief -- at least it is not a global phenomenon.
>
> Can't post the manifest, boss would get mad (not like it is any kind
> of secret, what with package interrogation being so easy...but...)
>
> I'll have to build up a test and keep adding things until I hi
Ward Willats wrote:
> SoI HOPE NO ONE EVER CHANGES THE ENTRY ACTIVITY OF THEIR PROGRAM
> WHEN THEY ISSUE AN UPDATE OR THEIR USERS ARE GOING TO HAVE TO ERASE
> THEIR PHONES.
I don't think it's quite that simple.
I am able to somewhat reproduce this problem. I say "somewhat" because:
1. It
Well crap.
I changed the entry activity (MAIN, LAUNCHER) to my app in the
manifest (swapped it with another activity, actually).
Install. Android tries to launch the old entry activity.
Uninstall, reinstall -- no change.
Factory reset the phone -- install -- NEW ENTRY ACTIVITY RECOGNIZED!
Sw
5 matches
Mail list logo
