[Bug] Remote Config FetchAsync throws exception with TimeSpan

[Nyankoo]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2020.3.18f1
• Firebase Unity SDK version: 8.1.0
• Source you installed the SDK: Unity Package Manager
• Problematic Firebase Component: Remote Config
• Other Firebase Components in use: Firestore, Crashlytics, Auth
• Additional SDKs you are using:
• Platform you are using the Unity editor on: Windows
• Platform you are targeting: Android (Unity Editor is also affected)
• Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:

When setting the cache expiration of FetchAsync() to TimeSpan.Zero (or any other TimeSpan), an exception is thrown with ErrorCode 1. The Message parameter is empty.

Steps to reproduce:

Relevant Code:

await FirebaseRemoteConfig.DefaultInstance.FetchAsync(TimeSpan.Zero); //This (or any other TimeSpan) will result in an exception

[paulinon]

Hi @Nyankoo,

Thanks for reporting this issue. Version 8.2.0 of the SDK has been released recently. Could you verify if the issue persists there as well? If it does, please provide a minimal, reproducible example of your project along with the complete steps to replicate this behavior.

[Nyankoo]

@paulinon Did something in Version 8.2.0 change related to Remote Config? The changelog doesn't mention anything.

[paulinon]

Hi @Nyankoo,

While the release notes don't mention anything related to Remote Config, this is to ensure that the issue persists even with the latest updates and fixes.

I look forward to your findings.

[DanForstinger]

I can confirm we are seeing this issue, on 8.2.0. It's causing our app to fully hang.

We are sending in a timespan of 1 minute. We started seeing this about 4 weeks ago. Can confirm removing the timespan argument stopped the issue from happening, but we can't wait for ~12 hours for remote config updates!

Should be simple enough to reproduce in an empty project on your end.

[Nyankoo]

@paulinon We didn't had a change to update, but Dan's report shows that this is also happening with 8.2.0.