On May 16, 2:23 pm, Mark Murphy <[email protected]> wrote: > First, it may be that pushing out a regular update to the RemoteViews > will suffice, no different than your regular app widget update process.
I don't think this will work, since IIRC an update doesn't affect it. Which would make sense if the host is linked to the old version of the package. > If that is insufficient, you can probably achieve a similar end by > pushing out an update with a totally different layout (e.g., an empty > one) and, milliseconds later, pushing out a regular update back to your > desired layout. You could use AlarmManager to schedule the second update. Interesting idea, something to try. Thanks for the suggestions Mark. This has to be a general problem though, it seems like it would affect everyone. And clearly it's not all that unusual for resource IDs to shift around. I'll have to try to reproduce it and see if that's really it, but it would help if I knew whether others have run into this. -- 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
