You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
App-only daily offers are missing from the parsed dashboard #603
Daily "Rewards app only" offers are invisible to the script — and can't be earned from the web
Since 2026-09-04 the dashboard shows 5 extra daily offers worth 10 points each
(offerId pattern: WW_Moreactivities_RewardsApp_offer_YYYYMMDD_1..5), titled
"... (only in the Rewards app)". The web UI shows them as locked.
Two separate findings:
The script never sees them. They ARE present in
rewards.bing.com/api/getuserinfo?type=1 under dashboard.morePromotions, and
they pass MorePromotions.isActionable() as written:
complete: false
pointProgressMax: 10
promotionType: "urlreward"
priority: 1
exclusiveLockedFeatureStatus: "notsupported" (note: not "locked")
attributes.is_unlocked: "False"
But they are absent from the dashboard payload the bot bootstraps, so
MorePromotions reports "remaining=3" while the API lists 8 actionable items.
I confirmed this by diffing API snapshots taken before and after a run.
Even so, they look deliberately gated: every destinationUrl of these offers
carries &rnoreward=1, which regular urlreward offers do not. Completing them
manually in the Rewards app sets complete: true and awards the points, while
attributes.is_unlocked stays "False" — so that field means "reachable from
the web", not "done".
Two questions:
a) Is it worth surfacing these somewhere (e.g. a log line saying N app-only
offers were skipped), so users understand why ~50 points/day appear to be
missing? Right now the script is silently correct but looks broken.
b) Do you see any legitimate route to completing them without the app, or is
rnoreward=1 a hard gate by design? If it is a hard gate, I'd rather have it
documented as out of scope than have people chase it.
Side note: is_unlocked is declared in DashboardData.ts but never read anywhere.
Yes, they suddenly changed part of the completion requirements. Now you have to complete the tasks through the Rewards app in the Microsoft Store. I'm not sure how to handle this.
Update: the format changed on 2026-09-27, so the details in my original report are outdated.
The daily WW_Moreactivities_RewardsApp_offer_* offers are gone. They were replaced by a weekly punch card, up to 70 points per week (Italian UI title: "Missione esclusiva settimanale dell'app Rewards").
Location: dashboard.punchCards in rewards.bing.com/api/getuserinfo?type=1, no longer morePromotions
all children are promotionType: "urlreward", and the seven daily ones still carry rnoreward=1, so opening them from the web doesn't award points
attributes.is_unlocked stays "False" even on completed children, so it can't tell which ones are available
New:
one child unlocks per day starting on Sunday. The weekday is only encoded in the offerId; the web panel shows future ones with a padlock
the /earn RSC payload only contains the parent, the children are only in getuserinfo
the children don't appear in the Bing flyout response (/rewards/panelflyout/getuserinfo?channel=BingFlyout) either, so the sidebar route mentioned above may not apply to the new format. I only checked the response, not the sidebar UI itself.
As far as I can tell, #612 targets the /earn cards and Explore on Bing rather than these app-only activities, so this issue probably shouldn't be closed by it.
As far as I can tell, #612 targets the /earn cards and Explore on Bing rather than these app-only activities, so this issue probably shouldn't be closed by it.
Thanks for the detailed update.
You were completely right that PR #612 initially only addressed the new /earn RSC payload and Explore on Bing.
However, I just pushed an update to the PR branch that specifically resolves the new weekly RewardsApp punch card. The problem with these cards was in PunchCards.ts: isClaimChild was matching reward inside WW_pcchild{N}_urlreward_..., mistakenly classifying these daily activities as reward claim buttons and trying to POST to the claim endpoint instead of running them.
With that fixed, the bot now correctly recognizes and executes the unlocked daily children as regular UrlReward activities, allowing them to credit properly day by day.
So PR #612 now covers both the /earn tab overhaul and this weekly RewardsApp punch card, directly addressing #603.
Activity
[-]Rewards app only[/-][+]App-only daily offers are missing from the parsed dashboard[/+]2oTA commentedon Sep 6, 2026
Yes, they suddenly changed part of the completion requirements. Now you have to complete the tasks through the Rewards app in the Microsoft Store. I'm not sure how to handle this.
shmily1866 commentedon Sep 10, 2026
This seems to be a new type of activity, so I’d like to request support for it.🙏😊
phanex commentedon Sep 10, 2026
There is. You need to perform any Bing search, press this button to call rewards sidebar:
And here is it:
TheNetsky commentedon Sep 10, 2026
I'm currently unavailable till Sunday, after I will be back to look at this and other issues.
TheNetsky commentedon Sep 13, 2026
I'll be looking into this.
phanex commentedon Sep 15, 2026
It looks like all these things are now in the "Earn" tab rather than the dashboard: https://rewards.bing.com/earn
LepaBrenaa commentedon Sep 17, 2026
@phanex is there a way for me to contact you? I got a question regarding your setup since you seem to be from the same country as me.
fix(rewards): add support for new /earn dashboard and Explore on Bing…
fix(rewards): add support for new /earn dashboard and Explore on Bing…
fix(rewards): add support for new /earn dashboard and Explore on Bing…
topsq commentedon Sep 29, 2026
Update: the format changed on 2026-09-27, so the details in my original report are outdated.
The daily
WW_Moreactivities_RewardsApp_offer_*offers are gone. They were replaced by a weekly punch card, up to 70 points per week (Italian UI title: "Missione esclusiva settimanale dell'app Rewards").dashboard.punchCardsinrewards.bing.com/api/getuserinfo?type=1, no longermorePromotionsWW_pcparent_RewardsApp_weekly_Exclusive_Septw4_2026_punchcardWW_pcchild{N}_urlreward_{Day}_RewardsApp_weekly_Exclusive_Septw4_2026_punchcard, where{Day}isInstall, thenSunday…SaturdaySnapshot taken on 2026-09-29 (a Tuesday):
Still true from the original report:
promotionType: "urlreward", and the seven daily ones still carryrnoreward=1, so opening them from the web doesn't award pointsattributes.is_unlockedstays"False"even on completed children, so it can't tell which ones are availableNew:
/earnRSC payload only contains the parent, the children are only ingetuserinfo/rewards/panelflyout/getuserinfo?channel=BingFlyout) either, so the sidebar route mentioned above may not apply to the new format. I only checked the response, not the sidebar UI itself.As far as I can tell, #612 targets the
/earncards and Explore on Bing rather than these app-only activities, so this issue probably shouldn't be closed by it.phanex commentedon Sep 29, 2026
Thanks for the detailed update.
You were completely right that PR #612 initially only addressed the new /earn RSC payload and Explore on Bing.
However, I just pushed an update to the PR branch that specifically resolves the new weekly RewardsApp punch card. The problem with these cards was in
PunchCards.ts:isClaimChildwas matchingrewardinsideWW_pcchild{N}_urlreward_..., mistakenly classifying these daily activities as reward claim buttons and trying to POST to the claim endpoint instead of running them.With that fixed, the bot now correctly recognizes and executes the unlocked daily children as regular
UrlRewardactivities, allowing them to credit properly day by day.So PR #612 now covers both the /earn tab overhaul and this weekly RewardsApp punch card, directly addressing #603.