Shared Objects behaving differently in Air 3.5

For those following along, here's a reply I just made in Lorenzo's other post on this topic.

I realize you have a workaround that you're using, but I also received the following info from the team today that I wanted to pass along.  This is being treated with high priority and we're hoping to have this addressed in a future 3.5 update.

The problem shows up when the tags <content> and <filename> in the application descriptor have different values (which is a common scenario). So an easy way for a developer to fix the problem for the time being would be to assign same values to these tags.

Thanks,
Chris