Edit the file /usr/share/gvfs/mounts/gphoto2.mount
and set AutoMount=true

Thanks for the suggestion but sadly it still doesn't work. When plugged in, PTP devices are still not showing up anywhere in Gnome Files but when I access them with the gphoto2:// link, they show up in sidebar just fine.

MTP devices are showing up when plugged, with or without AutoMount=true.

You might have to restart the service or to reboot

I did reboot but still no dice.

I'm getting this issue with an older Canon EOS Rebel XTi device as well as my OnePlus 2.

Manually able to access via gphoto2:// url, but not via a gvfs mount.

The android phone automounted fine when set to MTP mode, but would not automount when set to PTP mode.

I've been having the same issue with a rather old Canon reflex camera as well a couple weeks ago. It was at work and I had no time so I did not investigate much and instead just plugged the camera to another computer. Therefore I cannot give any relevant details, but just wanted to confirm having a similar issue although I could not investigate the real cause.

I have not tried with my own Sony cameras yet since I just recently installed Solus on the computer I usually use for photography at home. Will report back if having the same issue.

Doing some testing with for @tyzoid on IRC, I did some poking around- I tried putting a different command in that mount file, and to the best of my ability I can't find it getting executed. Also, I'm not sure how Nautilus handles MTP, but if it's through gvfs, then something strange is happening- it works perfectly even though AutoMount is set to false in /usr/share/gvfs/mounts/mtp.mount, just as was mentioned. Trash, however, is set to automount.- proving that it does make a difference. I feel like this isn't the right file to be editing. (No idea what is, but oh well..). Does this AutoMount just mean when the system starts, and not when plugged in as @kyrios123 implied?

Once I click on a device in nautilus, in MTP mode, this process shows up:

krc 5300 1 0 23:46 ? 00:00:00 /usr/lib64/gvfs/gvfsd-mtp --spawner :1.1 /org/gtk/gvfs/exec_spaw/9

I've also discovered upon using "nautilus gphoto2://[usb:xxx,xxx]" to view my ZTE Axon 7 in PTP mode (which works perfectly) that this process shows up:

krc 5410 1 0 23:48 ? 00:00:00 /usr/lib64/gvfs/gvfsd-gphoto2 --spawner :1.1 /org/gtk/gvfs/exec_spaw/10

Both of these are always running on both systems I've tried:

krc 1010 1 0 Aug21 ? 00:00:00 /usr/lib64/gvfs/gvfs-mtp-volume-monitor
krc 1037 1 0 Aug21 ? 00:00:00 /usr/lib64/gvfs/gvfs-gphoto2-volume-monitor

The only difference is that in MTP mode we get a shortcut, and in PTP mode we don't. Unfortunately, I don't really know what is responsible for figuring out that the device is there and telling Nautilus about it- from what I can tell, it's not udev as this is in userspace (?). My only thought is that it might be that gvfs-*-volume-monitor process? I don't know.

Sorry for the long post without a solution- I was just dumping the information I'd found. I hope it's useful to someone.. even if that's just me when I come back to it.

Same here with a Fuji X100T who works out of the box in Ubuntu 16.04
"nautilus gphoto2://[usb:001,003]" works also

Funny that this became a priority exactly a day after it happened to me.

I had the same issue with Xiaomi Mi Max 2 running all kinds of ROMs- stock, AOSP, etc.
Nautilus seems to have a problem with some devices. It didn't work in ubuntu in my case.

I run into this issue on my phone, PTP just doesn't work right. However, when I try to do it on other distros I have no problem. This is also impacting my ability to import photos using applications like Shotwell or GNOME Photos.

I don't have a device to test so after next sync, perform a full update, and see if PTP now works. Then try after a reboot and see if that changes anything before reporting back.

It does indeed work after the update! :) Thanks guys!