Skip to content
This repository has been archived by the owner on May 6, 2019. It is now read-only.

GZDoom folder is not created on first launch of the app #33

Open
mkrupczak3 opened this issue Jan 4, 2018 · 0 comments
Open

GZDoom folder is not created on first launch of the app #33

mkrupczak3 opened this issue Jan 4, 2018 · 0 comments

Comments

@mkrupczak3
Copy link

mkrupczak3 commented Jan 4, 2018

#Tested on Nougat API 25

Description:
It appears that the app attempts to create a GZdoom directory and config sub-directory before properly acquiring storage permissions from the user. Even after giving it permissions, the folder will not be created properly until the app is re-launched.

Steps to reproduce:
On first launch after the user taps "Allow" on the permissions request and navigates to the options fragment and taps the "RESET" button for the GZDoom folder a message appears saying "/storage/emulated/0/GZDoom is not a directory

Ideas to fix:
Have the app attempt to create the GZdoom directory directly after acquiring permissions (if it does not already exist)
Have the app attempt to create the GZdoom directory upon navigating to options fragment (if it does not already exist)
Have the app attempt to create the GZdoom directory upon navigating to any fragment (if it does not already exist)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant