You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON file should be treated as a text file and File Manager action should open the built-in text editor.
Actual behavior
JSONs are treated as archive files, what makes no sense. It opens the same window as for ZIP files, but shows nothing.
As an additional note: when I manually choose open as text file after selecting the file, it correctly opens the text editor. However, that adds unnecessary extra steps and I don't know any archive format that is saved as JSON.
Screenshots/Screen recordings
No response
Additional information
I don't know if it's of any relevance, but sometimes you may not have an action for JSON files from File Manager. I didn't have it when I had Material Files, but after uninstalling it, I see the Fossify File Maager's action again.
The text was updated successfully, but these errors were encountered:
Checklist
Affected app version
1.0.1
Affected Android/Custom ROM version
Android 13 (OxygenOS 13.1)
Affected device model
OnePlus 8 Pro
How did you install the app?
GitHub releases
Steps to reproduce the bug
Expected behavior
The JSON file should be treated as a text file and File Manager action should open the built-in text editor.
Actual behavior
JSONs are treated as archive files, what makes no sense. It opens the same window as for ZIP files, but shows nothing.
As an additional note: when I manually choose open as text file after selecting the file, it correctly opens the text editor. However, that adds unnecessary extra steps and I don't know any archive format that is saved as JSON.
Screenshots/Screen recordings
No response
Additional information
I don't know if it's of any relevance, but sometimes you may not have an action for JSON files from File Manager. I didn't have it when I had Material Files, but after uninstalling it, I see the Fossify File Maager's action again.
The text was updated successfully, but these errors were encountered: