Honestly, I wish that were the case, but I don't think so. This is the same build of our app that has been running for nearly a year now (updated last April). We've had no reports of this problem until just recently, which makes me think some security update changed something in parental controls that's causing this problem. Again, why it only happens on Rev-built apps, I don't know.
On Jan 28, 2010, at 3:03 PM, Sarah Reichelt wrote: > On Fri, Jan 29, 2010 at 4:47 AM, Chris Sheffield <cmsheffi...@gmail.com> > wrote: >> Jacque, >> >> Here's some more info from our end. Not sure if everyone is experiencing >> this same behavior or not, but in our case, the executable inside the app >> bundle is actually getting damaged. We compared an app that had been >> launched with parental controls enabled for it and one that hadn't, and the >> one that had was about 1 MB smaller. When trying to launch the executable >> directly from Terminal, we get a file read error. So in this case, it looks >> like no amount of messing with permissions is going to fix the problem. The >> file is toast at that point. > > > Is your app trying to write a file, being denied permission, so > over-writing the executable instead? > I encountered this with an app that was writing a preferences file > with the same name as the executable. When the path was set > incorrectly, the executable got replaced. > > Cheers, > Sarah > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution -- Chris Sheffield Read Naturally, Inc. www.readnaturally.com _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
