Qoder CN's Daily 100 Credits Were Missing; app.asar Shows a Server Flag Was the Real Gate
Users chasing Qoder CN's daily 100 Credits can waste a day on reinstalls when the actual gate is a server-side campaign flag that no local action can flip. The sensible response is to file feedback with logs or, for new accounts, wait for the next daily refresh; the docs conflict about QoderWork CN only adds to the confusion.
Qoder CN's daily 100 Credits are supposed to be claimable from the desktop client through a 'gift icon' in the usage panel. In stable build 0.4.11, that entry is actually labeled 'Benefits Center' (权益中心), and it is grayed out unless the server returns `hasClaimableCampaign: true`. The flag is not a local preference; it is fetched from an authenticated endpoint, which is why reinstalling or editing the client cannot bring back the claim button. The same app.asar strings show the client knows whether a campaign exists: the usage icon swaps between 'view my usage' and 'view my usage, there is a benefits campaign to claim'.
The campaign rules add their own constraints: the window is 10:00 Beijing time to 10:00 the next day, missed claims don't roll over, and each 100 Credits is separately valid for 30 days. Free, trial, and paid individual plans are eligible; enterprise subscriptions are not. Claiming is desktop-only, and the activity page lists eight products that accept the Credits while leaving out QoderWork CN, even though QoderWork CN's own documentation says Credits and plan benefits are shared across all Qoder products.
In the reported case, the gray cleared on its own the next day, and the only timeline variable was account creation the day before. The practical takeaway: fully restart the client, sign in with a personal account, or file feedback with logs, and for a brand-new account, wait for the next daily cycle before assuming something is broken.
Searching app.asar shows the client already knows whether a campaign is claimable; a user seeing only 'view my usage' isn't missing a hidden icon, the server simply hasn't enabled it for that account.
A brand-new account can go from grayed out on registration day to claimable the next day, which points to campaign eligibility lagging account creation, even for accounts that match the published rules.
Two official Qoder pages contradict each other on whether activity Credits work in QoderWork CN; doc drift like this turns a simple claim flow into a support ticket.
Electron's app.asar can be searched as plaintext, so UI labels and state flags are auditable without decompiling; that's a useful trick for diagnosing any client-side promotion UI.