Firebase Functions httpsCallable returns error on Android after every deploy of function

[henriquecf]

Hello. It is being a while since I am having this issue but I was not sure where it was coming from.

Every time I make a deploy to a cloud function, the first time I call this function after it has been deployed I get the following error from the plugin, even knowing that the function worked properly:

Error Caught: Error: com.google.android.gms.tasks.RuntimeExecutionException: java.net.SocketTimeoutException: timeout JS: com.google.android.gms.tasks.zzu.getResult(Unknown Source) JS: com.tns.Runtime.callJSMethodNative(Native Method) JS: com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1120) JS: com.tns.Runtime.callJSMethodImpl(Runtime.java:1000) JS: com.tns.Runtime.callJSMethod(Runtime.java:987) JS: com.tns.Runtime.callJSMethod(Runtime.java:967) JS: com.tns.Runtime.callJSMethod(Runtime.java:959) JS: com.tns.gen.com.google.android.gms.tasks.Continuation.then(Continuation.java:16) JS: com.google.android.gms.tasks.zzd.run(Unknown Source) JS: android.os.Handler.handleCallback(Handler.java:754) JS: android.os.Handler.dispatchMessage(Handler.java:95) JS: android.os.Looper.loop(Looper.java:165) JS: android.app.ActivityThread.main(ActivityThread.java:6375) JS: java.lang.reflect.Method.invoke(Native Method) JS: com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:883) JS: com.android.int...

To reproduce this is very easy. Call a function, deploy it on firebase and call it again on the app. The first time it is called again it returns this timeout error.

[henriquecf]

Hello again. I would like to know if I provided enough details to get my issue understood, as it is the first one I open here. I could provide more details if needed.

[EddyVerbruggen]

The question is clear, but the problem is not observed in my demo app.

What's the timeout set in your cloud function? Check https://console.cloud.google.com/functions/list?project=

Mine are set to 60 seconds.

Btw, Googling the issue seems to suggest this is not really a plugin issue. Unless the plugin makes the app crash?

[henriquecf]

Hello Eddy. This is strange indeed. When I searched for this I thought this was not a plugin issue either, but I am not sure anymore. I think this has something to do with the socket connection between the functions server and plugin, but I am not sure either with this problem is ocurring here or in the APK. But it is happening constantly with me.

It returns a rejection about 10 seconds later saying the error I mentioned above, and the strange is that people are saying this is the timeout for android (https://stackoverflow.com/questions/50971356/firebase-cloud-functions-change-timeout) which could really make it fail after a deploy

[EddyVerbruggen]

Hi, I noticed a delay in the availability of the function directly after a deploy as well, but I didn't hit that 10 sec timeout yet. It would be useful for me to know if that timeout crashes the app, or is the promise simply rejected?

Not sure what to do about this. Perhaps the plugin could auto-retry upon a timeout..

[henriquecf]

I think I forgot to say about that. The function processing happens normally in the cloud function. It works as normal. Just the client that times out and returns a rejection.

[henriquecf]

But in some cases this lets me in a complicated situation, as I rely on the answer to suppose everything went fine, so my users finish up duplicating some actions.

[EddyVerbruggen]

Oh, yeah, that's a good catch. So a retry is not what you want in that case. Hmm, then the only way is avoiding that timeout by somehow increasing it, but since we're using the Firebase SDK to call the function I don't think we can.

So if this only happens after a deploy (and possibly only for the first user to invoke the function?) perhaps calling the function yourself fixes it? That could be part of your deploy-script even.