I'm consistently having an issue with trying to install the new Foursquare Windows Phone app from the app store (version 126.96.36.199). The odd part is that this problem only happens with the Foursquare app. All other app upgrades and installs have been working fine for the past few weeks, except for this one.
I previously had the "old" design Foursquare app. When I got the notification to upgrade to the new design app, the app seems to download fine and then at the final step, it stops with an "Attention required" message. Clicking retry or cancelling the download doesn't make the error go away either. I uninstalled the Foursquare app (old school design), and tried to install it afresh from the app store, and that still didn't help.
I get an error code 80073cf9 (sometimes it's 80073cf6) which according to MSDN is an issue with app packaging / deployment (also see).
Other things I've tried to fix the problem, but which didn't try to work:
- Soft reset my phone
- Tried to sideload the app from my SD card (I get an error saying "Can't install company app: There's a problem with this company app. Contact your company's support person for help.")
- Changed the app install location from "phone" to "SD card" (and back)
- Wiped temporary files from both phone and SD card using Storage Sense
- This happens too quickly for me to take a screenshot, but might be relevant: after the app is downloaded, the next step in the app store download status says "Restoring data", then briefly shows "Finalising" before it fails. I've deleted my phone settings+app backup before installing, and that didn't help either.
The closest that I have come to a similar problem is a Reddit thread mentioning a similar problem when the app publisher name changed from "Nokia" to "Here Europe B.V.". In Foursquare's case, it previously used to be "Foursquare Labs, Inc." and is now "FOURSQUARE LABS".
Finally, I also filed a bug report with Foursquare and got this response from them:
We've heard of this problem from a number of WP users, but unfortunately it is an issue with Microsoft. You'll need to reach out to them in order to fix it.
I wonder if there's any fix (other than a hard reset - which may or may not solve the problem) which I'm missing?