Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote Config not producing throttling error accurately #12435

Closed
aj2109 opened this issue Feb 27, 2024 · 3 comments
Closed

Remote Config not producing throttling error accurately #12435

aj2109 opened this issue Feb 27, 2024 · 3 comments

Comments

@aj2109
Copy link

aj2109 commented Feb 27, 2024

Description

In trying to add non fatal logging specifically for throttling I have discovered what appears to be a bug. Whilst the error status of the connection is 429, as shown in the logs, and the catch let error as RemoteConfig hitting, its error code is never that of throttling (8002), its always internal errors code (8003). (minimumFetchInterval = 0 seconds btw)

Thanks!

Reproducing the issue

func forceThrottle() async {
        let RemoteConfig = RemoteConfig.remoteConfg()
       do {
       for i in 0...1000 {
          let foo = try await remoteConfig.fetchAndActivate()
       }
       } catch let error as RemoteConfigError {
       //prints false
           print("Error code is correct: \(error.code == .throttled)")
       } catch {}
}

Firebase SDK Version

10.21.0

Xcode Version

15.2

Installation Method

Swift Package Manager

Firebase Product(s)

AB Testing, Analytics, App Distribution, Crashlytics, Performance, Remote Config

Targeted Platforms

iOS

Relevant Log Output

10.21.0 - [FirebaseRemoteConfig][I-RCN000026] RCN fetch failure. Response http error code: 429

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@rizafran
Copy link
Contributor

Thanks for reporting, @aj2109. I tried to reproduce the issue and I was able to get the same error code (8003). I'll be raising this to our engineers to investigate.

@paulb777
Copy link
Member

Internally tracked at b/327637888

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants