hmmmm... should I just give up with tweetr then? I thought tweetr was the best swc I could find since it bundles with a twitter.swc that deals with sending tweets instead of having to painstakingly type out your own code that creates the tweet call. I'm still a little unclear when you mentioned that I won't have to deal with cross-domain.xml problems since my app is on air mobile (iphone).
i used the tweetr source files for a web app.
for an installed app (like air for iOS), you shouldn't have cross-domain problems. are you testing on an iDevice (you should be) or a simulator on a laptop (where you will have cross-domain issues)?