temporary fix for run app with correct id.

We have disabled syncfs currently. So this solution should work 100% of the time, since the app is always loaded from its real physical path.

@devoncarew 
We have an open issue to track syncfs being disabled (or, at least I assume we do). Can you reference this code from that issue? We want to be aware that when we re-enable syncfs, we'll have to do some work here to support running chrome apps living on a sync fs filesystem.