alyssaxuu/screenity · error · Error
File ID missing after upload
Error message
File ID missing after upload
What it means
After the resumable upload finished, the final Drive response supplied no file id, so the uploaded file cannot be referenced (shared, linked, or cleaned up). A validation guard thrown in runUploadOnce on the upload result.
Source
Thrown at src/pages/Background/drive/handleSaveToDrive.js:340
new Promise((resolve) =>
chrome.identity.removeCachedAuthToken({ token: stale }, resolve)
),
new Promise((resolve) => setTimeout(resolve, 2000)),
]);
}
} catch {}
const refreshed = await signIn();
if (!refreshed) throw new Error("Sign-in failed");
await chrome.storage.local.set({ token: refreshed });
token = refreshed;
} else {
token = await getAuthTokenFromStorage();
if (!token) throw new Error("Sign-in failed");
}
const folderId = await findOrCreateScreenityFolder(token);
const fileId = await uploadResumable(token, videoBlob, fileName, folderId);
if (!fileId) throw new Error("File ID missing after upload");
return fileId;
};
try {
diagEvent("drive-upload-start", {
blobSize: videoBlob.size,
blobType: videoBlob.type,
});
let fileId;
try {
fileId = await runUploadOnce(false);
} catch (err) {
if (isAuthError(err)) {
diagEvent("drive-auth-retry", {
error: String(err?.message || err).slice(0, 120),
});
fileId = await runUploadOnce(true);View on GitHub (pinned to 512606387b)
Solutions
- Log the full upload response to see which fields were actually returned
- Recover by listing the Screenity folder for the sanitized filename and using its id
- Treat it as a session anomaly and retry the upload once before failing
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/pages/Background/drive/handleSaveToDrive.js:340 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of alyssaxuu/screenity@512606387b (2026-09-02).
Data as JSON: /api/errors/3250947b278815b7.
Report an issue: GitHub.