Flutter个人资料页报错求助：TypeError及Firebase Firestore服务不可用问题

Let's tackle your two problems one by one, starting with the immediate TypeError that's breaking your profile page, then moving on to the Firestore service unavailable error.

1. Resolving the TypeError (type 'Future<dynamic>' is not a subtype of type 'Widget') #

What's causing this? #

Your buildprofileheader() function is marked as async, which means it returns a Future<Widget> instead of a direct Widget. Flutter's build method expects actual Widgets in the ListView children, not asynchronous futures. Additionally, there are a few bugs in your FutureBuilder implementation that need fixing.

Corrected Code for buildProfileHeader #

Replace your existing buildprofileheader function with this:

Widget buildProfileHeader() {
  return FutureBuilder<DocumentSnapshot>(
    future: userRef.doc(widget.userProfile).get(),
    builder: (context, snapshot) {
      if (snapshot.connectionState == ConnectionState.waiting) {
        return const CircularProgressIndicator(); // Use standard progress indicator
      }
      if (!snapshot.hasData || !snapshot.data!.exists) {
        return const Center(child: Text("User profile not found"));
      }
      
      // Parse the user data correctly
      UserModel user = UserModel.fromMap(snapshot.data!.data() as Map<String, dynamic>);
      
      return Padding(
        padding: const EdgeInsets.all(16.0),
        child: Column(
          children: [
            const Row(
              mainAxisAlignment: MainAxisAlignment.center,
              children: <Widget>[
                Icon(Icons.account_circle, size: 90,)
              ],
            ),
            Container(
              alignment: Alignment.center,
              padding: const EdgeInsets.all(12.0),
              child: Text(
                user.Username ?? "Unknown User", // Handle null username
                style: const TextStyle(
                  fontWeight: FontWeight.bold,
                  fontSize: 16.0,
                ),
              ),
            ),
          ],
        ),
      );
    },
  );
}

Key Fixes Made: #

• Removed the async modifier and changed the return type to Widget (since FutureBuilder is already a Widget that handles async operations)
• Fixed the document reference: Used widget.userProfile (the passed user ID) instead of userRef.id (which refers to the collection ID, not the user's document ID)
• Properly checked the snapshot state: Added handling for waiting state and missing data
• Corrected UserModel.fromMap to use the actual data from the snapshot (snapshot.data!.data() as Map<String, dynamic>)
• Added null safety for user.Username to avoid runtime errors

Update Your Build Method #

Make sure to call the corrected function (note the camelCase naming for consistency):

@override
Widget build(BuildContext context) {
  return Scaffold(
    appBar: AppBar(
      centerTitle: true,
      title: const Text("Profile"),
    ),
    body: ListView(
      children: <Widget>[
        buildProfileHeader(), // Now returns a valid Widget
      ],
    ),
  );
}

2. Fixing the FirebaseException ([cloud_firestore/unavailable] The service is currently unavailable) #

This error typically means your app can't connect to Firestore. Try these troubleshooting steps:

• Check your network connection: Ensure your device has a stable internet connection (Firestore requires online access for read/write operations unless you've enabled offline persistence).
• Verify Firebase configuration: Double-check that your google-services.json (Android) or GoogleService-Info.plist (iOS) is correctly added to your project and matches the configuration from your Firebase console.
• Check Firestore service status: Confirm there are no outages or maintenance for Cloud Firestore via Firebase's official status dashboard.
• Review Firestore security rules: Make sure your rules allow the current authenticated user to read the users collection. For testing, you can temporarily use these rules (replace with stricter rules for production):

  rules_version = '2';
  service cloud.firestore {
    match /databases/{database}/documents {
      match /users/{userId} {
        allow read: if request.auth != null && request.auth.uid == userId;
        allow write: if request.auth != null && request.auth.uid == userId;
      }
    }
  }
  

• Clear app cache/restart: Sometimes local cache can cause connection issues. Restart your app or clear its cache to reset the connection.
• Update Firebase dependencies: Ensure your pubspec.yaml has the latest versions of cloud_firestore, firebase_auth, and related packages. Run flutter pub upgrade to update them.

内容的提问来源于stack exchange，提问作者Abderrezak Douba