DIYgod/RSSHub · error · Error
未获取到数据!
Error message
未获取到数据!
What it means
Generic Error ('未获取到数据!' = 'No data retrieved!') thrown when the Miyoushe getUserFullInfo API returns a response whose data.data.user_info is missing. The upstream call succeeded at the HTTP level but the payload lacks the expected user_info object — typically an auth or invalid-uid response from Miyoushe.
Source
Thrown at lib/routes/mihoyo/bbs/cache.ts:28
uid ||= '';
const key = 'mihoyo:user-full-info-uid-' + uid;
return cache.tryGet(key, async () => {
const query = new URLSearchParams({
uid,
gids: '2',
}).toString();
const url = `https://bbs-api.miyoushe.com/user/wapi/getUserFullInfo?${query}`;
const response = await got({
method: 'get',
url,
headers: {
Referer: `https://www.miyoushe.com/ys/accountCenter/postList?id=${uid}`,
Cookie: config.mihoyo.cookie,
},
});
const userInfo = response?.data?.data?.user_info;
if (!userInfo) {
throw new Error('未获取到数据!');
}
const { nickname, introduce, gender, certification, avatar_url, uid: userId } = userInfo;
return {
nickname,
introduce,
gender,
certification,
avatar_url,
uid: userId,
};
});
};
export default { getUserFullInfo };
View on GitHub (pinned to bed535e087)
Solutions
- Refresh MIHOYO_COOKIE from a fresh miyoushe.com login.
- Verify the uid is a real Miyoushe user id (numeric, from the accountCenter URL).
- If persistent across valid cookies, the API envelope changed — report to route maintainers.
- Retry once; transient 200-with-error does happen.
Example fix
// before MIHOYO_COOKIE=stale_or_empty // after MIHOYO_COOKIE=account_id=12345; cookie_token=valid_token; ltoken=...
Defensive patterns
Strategy: retry
Validate before calling
// Validate the cookie is set before calling
if (!config.mihoyo.cookie) throw new ConfigNotFoundError('MIHOYO_COOKIE missing'); Type guard
function hasUserInfo(res: any): res is { data: { data: { user_info: object } } } {
return Boolean(res?.data?.data?.user_info);
} Try / catch
try {
const userInfo = response?.data?.data?.user_info;
if (!userInfo) throw new Error('No data from Miyoushe');
} catch (e) {
// refresh cookie / retry once Prevention
- Keep MIHOYO_COOKIE fresh.
- Retry once on empty-data responses.
- Log the retcode field from Miyoushe responses for diagnosis.
When it happens
Trigger: got(getUserFullInfo) resolves, but response.data.data.user_info is falsy. Common when the cookie is invalid (Miyoushe returns a logged-out payload), the uid doesn't exist, or the API shape changed.
Common situations: Invalid/expired MIHOYO_COOKIE so Miyoushe returns an unauthenticated envelope; uid refers to a deleted account; miyoushe changed its response envelope; transient API error returning an error body with HTTP 200.
Related errors
- 未获取到数据!
- mihoyo/bbs/official: getPostContent failed: ${url} - ${JSON.
- Details not found for product ${item.product_id}
- GetUserFullInfo is not available due to the absense of [Miyo
- 未获取到数据!
AI-assisted analysis of DIYgod/RSSHub@bed535e087 (2026-08-12).
Data as JSON: /api/errors/cb5b600fb55b34d9.
Report an issue: GitHub.