Hm the class files aren't really unpacked on disk. They exist as a single .dex file in the .apk. During install, a .odex file is created on disk -- this is the .dex file linked to the current platform code. When the VM loads your .apk, if the signature on the .dex inside doesn't match the .odex on disk it will try to re-create the one on disk... which will fail in a very clear way since normal apps doesn't have permission to write to the directory where they are stored.
On Thu, Aug 26, 2010 at 4:55 PM, William Ferguson <william.ferguson.au@ gmail.com> wrote: > Since it continues to occur after reboot it means there is a problem > with the the way the class files have been unpacked to disk. > > When an apk is installed and that app already exists, a temp folder > for the new instal is created, z and presumably the old instal is > removed later. > > It sounds like in some cases the new instal is being overlaid on the > existing app. Perhaps davlik segments static initialzers into separate > files and that's why you're seeing these symptoms. > > On Aug 26, 10:59 pm, TreKing <treking...@gmail.com> wrote: > > On Thu, Aug 26, 2010 at 3:31 AM, mot12 <martin.hu...@gmail.com> wrote: > > > The problem with null pointers I can also see with my users. > > > > I now have 19 more reports of the same problem in the Dev Console for the > > free version and 16 for the paid version. Same stack trace, same > > NullPointerException. > > > > > I don't understand the above comment about statics either. > > > Uninstalling the app presumably means that app being closed first. The > > > updated version needs to be started by the user, it doesn't > > > automatically replace what was in memory before. > > > > Agreed, especially since users report the issue continues after a phone > > reboot. Re-install is the only solution. > > > > But it may be related to static data somehow. The null pointer people are > > reporting is supposed to be set from a static list of predefined objects > and > > I just added this new static data in the last release, which probably > > explains the surge in problems since last time. It's like the new static > > data is being corrupted somehow. > > > > > --------------------------------------------------------------------------- > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices > > -- > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
