Since XAP deployment is cumbersome:
| Issue | Cause | Workaround |
|-------|-------|-------------|
| "Can't log in" | OAuth/SSL/TLS mismatch | Use WebView wrapper (Option B) |
| "Error checking for updates" | Dead Microsoft services | Ignore; sideload manually |
| App crashes on launch | Expired digital signature | Re-sign XAP with a self-signed cert (for dev unlocked phones) |
| White screen after login | Broken JavaScript API | Clear WebView cache or use mbasic version |
Do not expect a fully functional "new" Facebook XAP.
The only reliably working method in 2025+ is a WebView wrapper pointing to Facebook's basic HTML site. Official API-based XAPs are permanently broken.
If you need this for archival or demonstration purposes, follow the Web Wrapper creation steps above. For actual social networking, upgrade to an Android/iOS device or use a PC browser.
The blue light of the Nokia Lumia 920 flickered in the dark bedroom, casting a sharp glow over Marcus’s face. It was 2:00 AM in 2024, years after Microsoft had officially pulled the plug on Windows Phone. To most, the device was a paperweight. To Marcus, it was a challenge.
He wasn't looking for a trip down memory lane; he was looking for a way back in. He spent his nights on obscure forums and Telegram channels where "Lumia lovers" still gathered. The holy grail of their community was a working Facebook client. The official app had been dead for years, showing nothing but a "Connection Error" screen.
Then, a notification popped up on an old XDA Developers thread. The title was simple: facebook_windows_phone_v10.1_revived.xap (NEW). The Discovery
Marcus felt a rush of adrenaline. In the world of Windows Phone, a .xap file was the magic key—the application package format used for Windows Phone 7 and 8. facebook windows phone xap new
The Source: A user named MetroGhost claimed to have re-coded the API calls.
The Promise: A native experience with working notifications and image uploads.
The Risk: Side-loading unverified files could brick the phone or compromise his data.
He didn't care. He connected his Lumia to his PC, opened the WP8.1 SDK deployment tool, and watched the progress bar crawl across the screen. The Installation
The deployment tool reached 100%. Marcus looked at his phone. There, nestled between the Spotify tile and the camera, was the familiar blue "f" logo. It looked crisp. It looked alive. He tapped the tile.
The splash screen didn't crash. Instead, the Live Tile flipped, showing a tiny preview of a notification. The "Metro" interface—those bold fonts and horizontal scrolling panoramas—stretched across the screen. It was beautiful. While the rest of the world moved to rounded corners and cluttered menus, this app stayed true to the minimalist, typographic soul of Windows Phone. The Ghost in the Machine
As Marcus scrolled through his feed, he realized something strange. The app was fast—faster than Facebook had ever been on this hardware. But as he looked closer at the posts, he saw updates from people he hadn't spoken to in a decade. Since XAP deployment is cumbersome:
Status updates from 2013 appeared as if they were posted minutes ago.
Photos of old parties and long-gone cafes filled the screen. The Chat function pinged.
A message bubble appeared. It was from a friend who had passed away three years prior. The message read: "The UI looks great, doesn't it? Glad you finally got it working." The Reality
Marcus dropped the phone. The screen cracked, a spiderweb of glass fracturing the blue interface. He realized the "new" XAP wasn't just a patched app. It was a digital time capsule that had somehow bridged the gap between the dead servers of the past and the reality of the present.
He looked at his PC. The forum post from MetroGhost was gone. The thread was marked "404 Not Found."
He picked up the shattered Lumia. The screen was still glowing. Even through the cracks, the Live Tile for Facebook was spinning, showing more notifications from a world that no longer existed. He realized that for some, the Windows Phone era never truly ended—it just moved to a place where the servers never go down. AI responses may include mistakes. Learn more
This isn't a native XAP but a web wrapper packaged as an APPX that mimics a native app. It allows you to inject custom user agents to trick Facebook into sending the "Touch" version of the site. This isn't a native XAP but a web
Why it's "New": The wrapper updates the WebView control to Edge Chromium (via a hack), allowing modern JavaScript to run.
If you want a working Facebook launcher today:
After building your app:
By: Windows Phone Legacy Archive
In the graveyard of mobile operating systems, few platforms inspire as much nostalgic tinkering as Windows Phone. Its radical typography, live tiles, and buttery-smooth interface (even on cheap hardware) still command a cult following. However, the biggest hurdle for any user picking up a Lumia 1020, 930, or 640 today is the "app gap."
Nowhere is this more painful than with Facebook. Microsoft officially pulled the plug on the Windows Phone 8.1 and Windows 10 Mobile stores for many legacy devices. The built-in Facebook app errors out; the login screen loops forever.
If you are desperately searching for a "Facebook Windows Phone XAP new" —hoping to find a fresh, working installation file—you have arrived at the right place. This guide covers the history of the app, where to find the last "new" builds, and how to side load them.