macOS RetroArch manually setting path / pointing at .app file does not recognize it.

[networked47]

Mac Mini M2 Pro
macOS: 26.3.1 (25D2128)

To replicate:

• Have RetroArch installed in non-standard location
• Open RetroMultiTools
• Go to Settings
• Click Auto-Detect on RetroArch Integration
  (returns: RetroArch not found. Please browse manually or download it)
• Click Browse
• Navigate to where RetroArch.app i located
• Click OK.
  (no chaange in Path box)
• or double click on .app
  (no change in Path box)

As a consequence Core Downloader does not work as expected.

[SvenGDK]

Mac Mini M2 Pro macOS: 26.3.1 (25D2128)

To replicate:

• Have RetroArch installed in non-standard location
• Open RetroMultiTools
• Go to Settings
• Click Auto-Detect on RetroArch Integration
  (returns: RetroArch not found. Please browse manually or download it)
• Click Browse
• Navigate to where RetroArch.app i located
• Click OK.
  (no chaange in Path box)
• or double click on .app
  (no change in Path box)

As a consequence Core Downloader does not work as expected.

The .app should now be detected in v2.0, there was an issue that prevented taking the .app in account.

[networked47]

I stil get the same error.

Way to replicate is the same.

However I have an idea, since the .app is a container for the files and the executrable, and when either double-clicking on the .app or clicking open on the dialog closes the window, it never really 'opens' the .app for navigation to the Contents/MacOS structure and thus fails in the detection.

(on note: using the self-contained installer)

[SvenGDK]

I stil get the same error.

Way to replicate is the same.

However I have an idea, since the .app is a container for the files and the executrable, and when either double-clicking on the .app or clicking open on the dialog closes the window, it never really 'opens' the .app for navigation to the Contents/MacOS structure and thus fails in the detection.

(on note: using the self-contained installer)

That's strange, just tested it again with latest RetroArch build on my MBP with 10.15 (Catalina) and it get's auto-detected from /Applications/RetroArch.app/Contents/MacOS/RetroArch

[networked47]

I do have it installed in another path, it's the first step in my "how to replicate".

That the auto-detect doesn't find it I completely accept, unless it were to do a scan of the disk and all attached volumes. And that would be silly.

But since you can point out a path, I used that and that part doesn't work/fails to find it, even when pointed out the path or the .app file.

[SvenGDK]

I do have it installed in another path, it's the first step in my "how to replicate".

That the auto-detect doesn't find it I completely accept, unless it were to do a scan of the disk and all attached volumes. And that would be silly.

But since you can point out a path, I used that.

Yes I edited after reading again and could reproduce the bug, I first tought manually choosing and pressing auto-detect would resolve the manually selected path but it doesn't. Will fix this.

[SvenGDK]

I do have it installed in another path, it's the first step in my "how to replicate".

That the auto-detect doesn't find it I completely accept, unless it were to do a scan of the disk and all attached volumes. And that would be silly.

But since you can point out a path, I used that and that part doesn't work/fails to find it, even when pointed out the path or the .app file.

There's a temporary fix that should accept your custom RetroArch installation path :

1. Open the file /Users/YOURUSERNAME/Library/Application Support/RetroMultiTools/settings.json
2. Find the "RetroArchPath" entry and add your custom RetroArch.app path between "" like "/Users/svengdk/Downloads/RetroArch.app/Contents/MacOS/RetroArch"
3. Restart RetroMultiTools