Skip to content

Stop save-mode exports landing as (invalid).json - #40

Merged
MisterGatto merged 1 commit into
skyprotocol:osp-masterfrom
HugeFrog24:osp-master
Aug 20, 2026
Merged

Stop save-mode exports landing as (invalid).json#40
MisterGatto merged 1 commit into
skyprotocol:osp-masterfrom
HugeFrog24:osp-master

Conversation

@HugeFrog24

Copy link
Copy Markdown
Contributor

Every save-mode export through the selector lands as (invalid).json, and nobody chose that name. Here is how it happens:

  1. Canvas builds the save intent with a category, a MIME type, and a serene absence of any file name..
  2. The picker opens with the name field blank. The user shrugs and saves anyway.
  3. The provider is asked to create a document called "".
  4. AOSP refuses an empty name on a FAT-safe filesystem, so it swaps in a placeholder. That placeholder is the word (invalid). It is now the user's file name.
  5. Export again and the counter kicks in, so the folder fills with (invalid)(1).json, (invalid)(2).json.

The mod author gets the bug report and can do nothing with it, as the name was decided three layers below them. One extra on the intent fixes it.

…e via EXTRA_TITLE, avoiding the platform (invalid) fallback for an empty display name
@MisterGatto
MisterGatto merged commit 1352f3a into skyprotocol:osp-master Aug 20, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants