[Bug] macOS Bing Wallpaper fails to load in zh-CN locale due to HTTP/HTTPS conflict

Question

[Bug] macOS Bing Wallpaper fails to load in zh-CN locale due to HTTP/HTTPS conflict

t'aime je 95

Environment:

OS: macOS (Apple Silicon)

App Version: Bing Wallpaper 2.0.14

System Language: Simplified Chinese (zh-CN)

Symptom: The app homepage displays "Failed to load", and attempting to set the wallpaper prompts "Failed to set wallpaper".

Root Cause Analysis: By running the app binary in the terminal with RUST_LOG=trace, the following error is caught in the startup log: ERROR bingwallpaperapp_lib::scheduler: Initial rotation check failed: Only HTTPS URLs are allowed

The app strictly enforces HTTPS for images (the CSP also only allows https://*.bing.net). However, the backend API ([https://services.bingapis.com/ge-apps/api/v2/bwc/hpimages](https://services.bingapis.com/ge-apps/api/v2/bwc/hpimages)) returns http URLs when queried from the Chinese market (mkt=zh-CN), for example: [http://ts2.tc.mm.bing.net/th?id=](http://ts2.tc.mm.bing.net/th?id=)... For mkt=en-US, it correctly returns [https://www.bing.com/th?id=](https://www.bing.com/th?id=).... Because the zh-CN API returns HTTP, the app's own security policy blocks it. This also explains why users reported that temporarily switching the system language to English "fixes" the issue.

Temporary Workaround (No system language change required): Force the app to run in English via terminal: defaults write com.microsoft.bing.wallpaper AppleLanguages -array en-US Relaunching the app resolves the issue.

Suggested Fix:

Update the backend API to return https URLs for the zh-CN market.

OR: Make the client application automatically upgrade http to https for *.tc.mm.bing.net domains before fetching.Environment:
- OS: macOS (Apple Silicon)
- App Version: Bing Wallpaper 2.0.14
- System Language: Simplified Chinese (zh-CN)
Symptom: The app homepage displays "Failed to load", and attempting to set the wallpaper prompts "Failed to set wallpaper". Root Cause Analysis: By running the app binary in the terminal with RUST_LOG=trace, the following error is caught in the startup log: ERROR bingwallpaperapp_lib::scheduler: Initial rotation check failed: Only HTTPS URLs are allowed The app strictly enforces HTTPS for images (the CSP also only allows https://*.bing.net). However, the backend API ([https://services.bingapis.com/ge-apps/api/v2/bwc/hpimages](https://services.bingapis.com/ge-apps/api/v2/bwc/hpimages)) returns http URLs when queried from the Chinese market (mkt=zh-CN), for example: [http://ts2.tc.mm.bing.net/th?id=](http://ts2.tc.mm.bing.net/th?id=)... For mkt=en-US, it correctly returns [https://www.bing.com/th?id=](https://www.bing.com/th?id=).... Because the zh-CN API returns HTTP, the app's own security policy blocks it. This also explains why users reported that temporarily switching the system language to English "fixes" the issue. Temporary Workaround (No system language change required): Force the app to run in English via terminal: defaults write com.microsoft.bing.wallpaper AppleLanguages -array en-US Relaunching the app resolves the issue. Suggested Fix:
1. Update the backend API to return https URLs for the zh-CN market.
2. OR: Make the client application automatically upgrade http to https for *.tc.mm.bing.net domains before fetching.

0 个注释

1 个答案

你的答案

Answer 1

Hi t'aime je,

Note: This forum belongs to the Chinese-language Microsoft Q&A community. To help community members and moderators better assist you, it is recommended to post in Chinese rather than English.

Thank you for taking the time to investigate the issue and for providing such detailed findings, including the log output, reproduction conditions, root cause analysis, and workaround.

Based on your description, this appears to be a potential product issue with the Bing Wallpaper application rather than a configuration problem on your Mac. As Microsoft Q&A is a community support forum, we do not have access to the Bing Wallpaper engineering team and cannot verify or escalate product bugs directly.

I recommend submitting this report through the appropriate Bing support or Microsoft Support channels so that it can be reviewed by the responsible product team. When doing so, please include the log entry, locale-specific behavior, and the workaround you identified, as these details may assist their investigation.

Thank you again for sharing your findings with the community.