Facebook Login for Gaming to Instant Games (Zero Permissions)

<script src="https://connect.facebook.net/en_US/fbinstant.8.0.js"></script>

FBInstant.initializeAsync().then(function() {
  // Player is already authenticated. No login flow needed.

  // Load your game assets and report progress.
  FBInstant.setLoadingProgress(100);

  FBInstant.startGameAsync().then(function() {
    // Game is ready. Retrieve the player ID.
    var playerID = FBInstant.player.getID();
    startGame(playerID);
  });
});

• Display names and photos: Players’ names and avatars will change to their Facebook profile data. Use overlay views to display player names and photos rather than rendering them directly in your game canvas. See Overlay View Components for details.
• Player IDs: The Instant Games Player ID is game-scoped and differs from the legacy Facebook user ID.

// Player ID is always available after initializeAsync()
var playerID = FBInstant.player.getID();

// Connected players are always available (no permission needed)
FBInstant.player.getConnectedPlayersAsync().then(function(players) {
  // These are friends who also play your game
});

• Friends list: Replace Graph API /me/friends calls with FBInstant.player.getConnectedPlayersAsync().
• Sharing and activity: The Gaming Activity API is deprecated. Use FBInstant.updateAsync() and FBInstant.shareAsync() to share game events and custom updates.

1. Use FBInstant.player.getSignedPlayerInfoAsync('your_payload') on the client.
2. Send the resulting signature to your backend.
3. Your server must verify the signature using your App Secret.

FBInstant.player.getSignedPlayerInfoAsync('my_server_nonce')
  .then(function(result) {
    var signature = result.getSignature();
    // Send signature to your server for verification
    fetch('https://myserver.com/verify', {
      method: 'POST',
      body: JSON.stringify({ signature: signature })
    });
  });

1. Audit current integration. Identify all FB.login() calls, Graph API requests, and server-side access token verifications that must be replaced.
2. Plan data migration. Decide whether to implement account linking via ASIDs or allow a graceful restart. If linking, configure the Cross-play management tool in the App Dashboard.
3. Evaluate engine porting. If migrating a native mobile game, select an HTML5 framework (for example, Unity WebGL or Phaser) and scope the porting effort.
4. App Dashboard setup. Add the Instant Games product to your existing App ID.

1. Bundle restructuring. Create a self-contained bundle with index.html and fbapp-config.json.
2. SDK replacement. Remove the legacy Facebook JavaScript SDK and integrate fbinstant.8.0.js.
3. Implement loading flow. Replace login dialogs with initializeAsync(), setLoadingProgress(), and startGameAsync().
4. Update identity and server verification. Replace access token backend validation with getSignedPlayerInfoAsync() signature verification.
5. Migrate social APIs. Replace Graph API calls with getConnectedPlayersAsync(), shareAsync(), and updateAsync().
6. Implement data migration. If applicable, implement getASIDAsync() to map legacy ASIDs to the new Player ID and merge backend data.
7. Enable Zero Permissions. Toggle Zero Permissions in the App Dashboard to allow HTTPS communication with your backend.

1. Local testing. Test the core game loop locally using a mock SDK or local HTTPS server.
2. Platform testing. Upload the ZIP bundle to Web Hosting and test on the Facebook platform (iOS, Android, and desktop web).
3. Social testing. Use App Dashboard test users to verify that connected players and sharing features work correctly without permission prompts.
4. Data migration testing. Test the account linking flow to ensure legacy players do not lose their progress.
5. App review. Submit the game for Instant Games Quality Review and ensure all configurations (Privacy Policy, App Domains) are complete.
6. Push to production. Switch the App Mode to Live and push the tested bundle to production.

• Zero Permissions Overview — Understand the full capabilities of Zero Permissions.
• Bundle Configuration — Configure your game bundle.
• Player Identification Post Migration — Map player identifiers between your legacy app and Instant Games.
• SDK Reference — Full API documentation.
• Get Support — Reach out if you encounter issues during migration.