Conversation
|
If someone can reproduce the issue, their assistance would be greatly appreciated. This was a quick write up to workaround it if need be, but I'd like to address the root cause. The reporter said they are on Windows 10 for additional context. As I'm not able to reproduce, that makes me assume it could be potentially related. If it is related, my assumption would be we need to revisit how we are ensuring the paths are valid. |
Eblo
left a comment
There was a problem hiding this comment.
I have tested the issue in question, but I have no had luck in reproducing it. The behavior I see in 2.0.0 is that it will just prompt for and identify each ROM sequentially if you answer "No". The application certainly isn't doing "nothing".
I wonder if it was a path issue after all. While I cannot say whether this PR fixes that problem, I do like the option it presents as opposed to going through multiple ROMs sequentially.
Build Artifacts