This content has been marked as final. Show 4 replies
Bad form to reply to my own post, but I wanted to add that uninstalling and re-installing AIR and my app has no effect, and this is the first time the app is run after install, so there should be no code path (of mine) that these people get that everyone else doesn't. It seems as though the people who are hosed stay hosed.
Perhaps some webkit configuration problem, like this one that's a problem for Windows users and AIR 1.5?
Replying to my self again, there was a comment on the thread I linked in the first post that says:
"Try to remove any Input Managers (for example SIMBL) you may have installed (empty /Libary/InputManagers/ and ~/Libary/InputManagers/). The problem appears to be that some of those see that we’re using WebKit and think we’re Safari and try to patch the application in a way that makes it crash." (from Arno@adobe)
I'll ask some of the folks that had to problem to give it a shot and see if that's the silver bullet.
Most problems with WebKit we have found are related to Input Managers.
what does that mean input managers?
I've been getting this error trying to htmlLoader.loadstring into mx:html control......very frustrating