Error in Typescript cloud function: response object is not callable

Question

Error in Typescript cloud function: response object is not callable

My cloud function is structured like this:

// const {onSchedule} = require("firebase-functions/v2/scheduler"); // The Cloud Functions for Firebase SDK to set up triggers and logging.
    import * as logger from "firebase-functions/logger";
    const {onRequest} = require('firebase-functions/v2/https');
    
    exports.dailyShiftNotification = onRequest(async (req, res) => {
        const promise = fetch(`http://localhost:3000/api/messaging/dailyShiftNotification`, {
            method: 'POST',
        }).then(res => {
            if (!res.ok) {
              logger.error("There was an error sending messages");
              return res.status(500).send('Error sending messages');
            }
            return res.json();
        }).then(result => {
            return result;
        });
        
        try {
            const result = await promise;
            console.log(result);
            return res.status(200).send('Messages sent!');
        } catch (error) {
            console.error('Error:', error);
            return res.status(500).send('Error sending messages');
        }
    });

I'm encountering an issue where I can't return a response from my function, getting an error stating

this expression is not callable. Type 'Number' has no call signatures

I've attempted to address this by using

import { Request, Response } from 'express';

and setting res: Response, req: Request but it hasn't resolved the problem. Even after installing node-fetch and trying //ts-ignore, the function still times out without sending a response.

typescript next.js google-cloud-functions

Answer 1

Answer №1

The issue you're facing, as pointed out by Phil, is related to how you handle the response shadowing in the then() method. I suggest making some modifications to the overall formatting and functionality of your code, perhaps like this:

try {
 const response = await fetch(... rest of things) // Remove the THEN method
 if(!response.ok) { /* Handle errors as previously done in the then method */ }

 const result = await response.json();
 return res.status(200).send('Messages sent!');
} catch (e) {
 logger.error('Error:', e);
 return res.status(500).send('Error sending messages');
}

Answer 2

The issue you're facing, as pointed out by Phil, is related to how you handle the response shadowing in the then() method. I suggest making some modifications to the overall formatting and functionality of your code, perhaps like this:

try {
 const response = await fetch(... rest of things) // Remove the THEN method
 if(!response.ok) { /* Handle errors as previously done in the then method */ }

 const result = await response.json();
 return res.status(200).send('Messages sent!');
} catch (e) {
 logger.error('Error:', e);
 return res.status(500).send('Error sending messages');
}

Error in Typescript cloud function: response object is not callable

Answer №1

Similar questions

Retrieving data in Next.js

Exploring Typescript within React: Creating a property on the current instance

Finding the perfect pairing: How to align counters with objects?

What is the best way to include a new attribute in a TypeScript internal object?

Having difficulty retrieving data despite providing the correct URL

Tips for finalizing a subscriber after a for loop finishes?

Ways to invoke a function in an angular component from a separate component located in a different .ts file

Check if a string contains only special characters and no letters within them using regular expressions

By utilizing the HTML element ID to retrieve the input value, it is possible that the object in Typescript may be null

In React Native, you can pass native component properties as props, while also defining custom ones using a TypeScript interface

Attempting to capture a previously unhandled error thrown by Axios when utilized in conjunction with React Query (with suspense mode enabled) within a NextJs application

What's the method for validating the spread operator in Typescript?

Is it possible to utilize Webpack 5's ChunkGroup API with several entries?

Having trouble fetching information from a JSON file stored in a local directory while using Angular 7

Defining RefObject effectively in TypeScript

The issue of Next.js public/assets/css not loading is commonly experienced on dynamically generated pages

Transmit data via XMLHttpRequest in smaller portions or through a ReadableStream to minimize memory consumption when handling large datasets

After retrieving data successfully, the NextAuth Credentials function returns a null value

Verifying completed fields before submitting

The function to increase the number of days on a date in Angular is experiencing technical issues