Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Docs] Mini App wallet provider migration guide needed: Base App in-app browser (post-April 2026)

Open
#1,420 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
documentation

Research direction

Locate the mini-app wallet documentation and review its existing provider and SDK guidance first. Use the supplied Base App and Warpcast behavior, timeout patterns, upstream issue, and reference commit to add the migration section; done means the docs explain detection, injected-provider fallback, and safe handling of hanging SDK calls.

Written by the indexing model from the issue text.

Description

Problem

Base App's April 2026 update changed how mini-apps are launched: they now open in a standard in-app WebView instead of a Farcaster mini-app host. This is a breaking change for any mini-app that uses @farcaster/miniapp-sdk for wallet access.

The current docs don't cover:

  1. How to detect Base App in-app browser vs. true Farcaster embed (Warpcast)
  2. How to fall back to injected EIP-1193 provider (window.ethereum / coinbaseWalletExtension) in Base App
  3. The sdk.actions.ready() / sdk.wallet.getEthereumProvider() hang issue specific to Base WebView

This causes mini-apps to silently hang on transactions — no error, no timeout, just an indefinite loading state.

Suggested Addition

A "Wallet Provider Migration for Base App 2026" section in the mini-app docs covering:

Detection pattern
// Base App (post-April 2026) does NOT act as Farcaster mini-app host.
// sdk.isInMiniApp() returns false — use injected EIP-1193 instead.
async function getProvider(sdk) {
    const isEmbed = await Promise.race([
        sdk.isInMiniApp(),
        new Promise(resolve => setTimeout(() => resolve(false), 1000))
    ]);
    
    if (isEmbed) {
        return sdk.wallet.getEthereumProvider(); // Warpcast / true Farcaster host
    }
    
    // Base App or regular browser: use injected wallet
    return window.coinbaseWalletExtension 
        ?? window.ethereum 
        ?? null;
}
ready() timeout pattern
// In Base App, ready() never resolves — wrap with timeout:
await Promise.race([
    sdk.actions.ready(),
    new Promise((_, reject) => setTimeout(() => reject(), 5000))
]).catch(() => { /* continue, Base App doesn't need ready() ack */ });

Working Reference Implementation

This exact pattern was implemented and verified on Base mainnet in a real mini-app:

Impact

Any mini-app using @farcaster/miniapp-sdk for wallet transactions that:

  • Was built before April 2026
  • Relies on getEthereumProvider() from the SDK
  • Is listed in Base App discovery

...will silently break for all Base App users without this migration.

Related SDK Issue

Filed upstream: farcasterxyz/miniapps#608


Happy to contribute a PR with the docs addition if that would help.

Dominant language
JavaScript
Stars
337
Forks
798
Avg merge
19h 15m
Merged PRs (30d)
57

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from base/docs

All issues in base/docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.