Are we talking about the "Fix Broken File Paths" option that I added? File paths in Android are case sensitive, so I can't just treat them as case insensitive. It's perfectly valid to have two files with the same name but different case letters. Calls into the Android framework would fail if the case is wrong. On Windows 10, I could consider handling this differently though.
I'll see what I can do about the second part.
UPDATE:
I've changed the logic so that it tries to find the file whose path has the most matching characters at the end. Hopefully this will eliminate the problem you described.
I'll see what I can do about the second part.
UPDATE:
I've changed the logic so that it tries to find the file whose path has the most matching characters at the end. Hopefully this will eliminate the problem you described.