firebase-cloud-functions

Calls Firebase Cloud Functions from Flutter apps. Use when setting up callable functions, passing data to functions, handling errors from function calls, optimizing performance, or testing with the Firebase Emulator Suite.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "firebase-cloud-functions" with this command: npx skills add evanca/flutter-ai-rules/evanca-flutter-ai-rules-firebase-cloud-functions

Firebase Cloud Functions Skill

This skill defines how to correctly call Firebase Cloud Functions from Flutter applications.

When to Use

Use this skill when:

  • Setting up and configuring Cloud Functions in a Flutter project.
  • Calling callable functions and handling their results.
  • Handling errors from function calls.
  • Optimizing function call performance.
  • Testing with the Firebase Emulator Suite.

1. Setup and Configuration

flutter pub add cloud_functions
import 'package:cloud_functions/cloud_functions.dart';

// After Firebase.initializeApp():
final functions = FirebaseFunctions.instance;
  • Initialize Firebase before using any Cloud Functions features.
  • For region-specific deployments, specify the region when getting the instance.
  • Deploy callable functions to Firebase before attempting to call them from your Flutter app.
  • Consider implementing App Check to prevent abuse of your Cloud Functions.

2. Calling Functions

Use httpsCallable to reference a function, then call to invoke it:

final result = await FirebaseFunctions.instance
  .httpsCallable('functionName')
  .call(data);
  • Pass data as a Map — it is automatically serialized to JSON:
final result = await FirebaseFunctions.instance
  .httpsCallable('addMessage')
  .call({
    "text": messageText,
    "push": true,
  });
  • Access the result via the data property — it is automatically deserialized from JSON:
final responseData = result.data;
// Cast to expected type if needed:
final responseString = result.data as String;
  • Do not pass authentication tokens in function parameters — they are automatically included by the SDK.
  • Keep function names consistent between client code and server-side implementations.

3. Error Handling

Always wrap function calls in try-catch and check for FirebaseFunctionsException:

try {
  final result = await FirebaseFunctions.instance
    .httpsCallable('functionName')
    .call(data);
  // Handle successful result
} catch (e) {
  if (e is FirebaseFunctionsException) {
    print('Error code: ${e.code}');
    print('Error message: ${e.message}');
    print('Error details: ${e.details}');
  } else {
    print('Error: $e');
  }
}
  • Handle network connectivity issues and timeouts appropriately.
  • Provide meaningful error messages to users when function calls fail.
  • Consider implementing retry logic for transient errors.

4. Performance Optimization

Set a timeout appropriate to the expected execution time:

final callable = FirebaseFunctions.instance.httpsCallable(
  'functionName',
  options: HttpsCallableOptions(
    timeout: const Duration(seconds: 30),
  ),
);
  • Minimize the amount of data passed to and from functions to reduce latency.
  • Use batch operations when possible to reduce the number of function calls.
  • Consider client-side caching for frequently used function results.
  • Monitor function performance in the Firebase Console to identify bottlenecks.
  • Account for cold starts for infrequently used functions.
  • Implement proper loading states in the UI while waiting for function responses.

5. Testing and Development

Use the Firebase Emulator Suite for local development and testing:

FirebaseFunctions.instance.useFunctionsEmulator('localhost', 5001);
  • Test functions with both valid and invalid inputs to ensure proper validation.
  • Verify that functions handle authentication correctly.
  • Test with different user roles and permissions to ensure proper access control.
  • Implement unit tests for client-side function calling logic.
  • Use integration tests to verify end-to-end function behavior.

References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

effective-dart

No summary provided by upstream source.

Repository SourceNeeds Review
General

riverpod

No summary provided by upstream source.

Repository SourceNeeds Review
General

firebase-crashlytics

No summary provided by upstream source.

Repository SourceNeeds Review