Self reporting the problem.
Observable on desktop, probably also applicable on mobile.
With Obsidian 1.7.5 there must have come some more not backward-compatible changes...
When the File Explorer view is not displayed initially (e.g. a different view is active in the pane) the custom sort plugin cannot apply the custom sort. In result when the File Explorer view is activated, the custom sorting order is not there. This is a know side effect of breaking changes introduced in Obsidian 1.7.2 - the Deferred Views concepts, a performance optimization in Obsidian.
So far (up to Obsidian 1.7.4) the workaround was simple, it was enough to manually apply the custom sort (via ribbon icon or via sort on command) after showing the File Explorer view. Starting with Obsidian 1.7.5 the workaround no longer works, using ribbon icon or the command has no effect. Additionally an error started appearing in the console:
The workaround for 1.7.5 is to disable the custom sort plugin in the vault settings and re-enable it. Fortunately it helps. Invonvenient, I know...
Self reporting the problem. Observable on desktop, probably also applicable on mobile.
With Obsidian 1.7.5 there must have come some more not backward-compatible changes...
When the File Explorer view is not displayed initially (e.g. a different view is active in the pane) the custom sort plugin cannot apply the custom sort. In result when the File Explorer view is activated, the custom sorting order is not there. This is a know side effect of breaking changes introduced in Obsidian 1.7.2 - the Deferred Views concepts, a performance optimization in Obsidian.
So far (up to Obsidian 1.7.4) the workaround was simple, it was enough to manually apply the custom sort (via ribbon icon or via sort on command) after showing the File Explorer view. Starting with Obsidian 1.7.5 the workaround no longer works, using ribbon icon or the command has no effect. Additionally an error started appearing in the console:
The workaround for 1.7.5 is to disable the custom sort plugin in the vault settings and re-enable it. Fortunately it helps. Invonvenient, I know...