u/thomas_dao

Update on the recent sign-in issue and our infrastructure progress

Hi everyone,

A few weeks ago, many users were unable to sign in to UpNote. The issue was caused by a large number of requests from automated bots, which consumed the quota assigned to our Firebase project and prevented our users from signing in. After the quota reset for the day, users were able to sign in again, but the issue would happen again whenever the quota was exhausted.

Since then, we have strengthened our service to better identify bots and real users using Cloudflare verification. The result so far has been encouraging. After version 9.19.0 was released, we saw the Firebase quota usage drop significantly, and the unable-to-sign-in issue has not happened again.

Building on that, we recently released version 9.21.0 with further changes to protect our service from automated bots. We want to give everyone enough time to update, so please update UpNote to the latest version within the next 7 days. After that, older versions of the app will no longer be able to sync data with the server.

We also want to share a little about what we’re working on. We have been building our own server infrastructure so that we can gradually migrate core components away from Firebase. Bug fixing is still important and we will continue to address serious issues in a timely manner, but most of our development effort right now is focused on making the new infrastructure as stable and reliable as possible.

The good news is that the new infrastructure is progressing well and we hope to start testing it soon. It will take some time to make sure the new service works reliably before we can move forward with the migration.

As we continue this transition, some future changes may not be compatible with older versions of UpNote. Please keep UpNote updated to the latest version to make sure the app can continue to sync and work properly. We will try to give users enough time to update whenever such changes are required.

Thank you for your understanding and support.

reddit.com
u/thomas_dao — 8 days ago

App Check return Invalid request. Error: Quota exceeded for quota metric

Hello,

We are currently seeing a massive number of requests targeting our Firebase project, especially the Sign in with Password and Generate Custom App Check Token endpoints. We are observing nearly 18 million requests, which is clearly abnormal.

At the moment, clients are unable to generate App Check tokens. Every request immediately fails with the following error:

“Invalid request. Error: Quota exceeded for quota metric ‘Token exchange requests’ and limit ‘Token exchange requests per day’ of service ‘firebaseappcheck.googleapis.com’ for consumer ‘project_number: xxxxxx’.”

However, when we check the project dashboard at https://console.cloud.google.com/apis/api/firebaseappcheck.googleapis.com/quotas, the App Check quota is still shown in green and does not appear to be exhausted.

This issue is urgent and is severely affecting our users, as they are unable to sign in.

If possible, could you temporarily increase the App Check quota for our project while this issue is being investigated?

We are a Blaze customer and have been dealing with an extremely high volume of requests targeting our authentication endpoints for a long time. We adopted App Check because it was intended to mitigate this type of abuse. Unfortunately, it has now become a single point of failure, since every sign-in requires generating an App Check token first.

Thank you for your urgent assistance.

reddit.com
u/thomas_dao — 1 month ago