Go to “Settings” on the iPhone > Photos > Wireless Data.Or if you are using cellular data for uploading photos, make sure that data is enabled on your iPhone. If there’s something wrong with the WiFi, try to fix it before syncing. Check if there’s an available WiFi or Cellular option on the device. If your photos are not syncing to iCloud, there’s a good chance the internet isn’t connected to which may be preventing the sync. This is usually a connection issue or a storage issue. If your iCloud Photos are not syncing, typically, one of two things will resolve it. What to do if your iCloud Photo Library is not syncing Fortunately, there are a few ways to fix syncing issues with iCloud photos across devices and platforms to avoid you losing any precious photos. Images may fail to upload or get misplaced, which means users may need to recover photos from iCloud. Sometimes syncing problems occur with iCloud. However, like any tech device or software, you can sometimes have issues. Create a photo album in the iPhone Photos app, and it simultaneously appears in the Mac photo albums, too. Take a photo on an iPhone, and it automatically appears on an iPad. Now it synchronizes happily.ICloud is the smart, efficient way to store your photos thanks to it’s ability to sync in real-time. So thank you, was able to resolve the name issue by simply removing the underscore from the share name I use for PhotoSync. This was made possible by the great help of by turning the SMB error collection setting to full (Services -> SMB -> Log Levels) followed by him looking through the debug log files once I had fired up PhotoSync on my iPhone, tried to setup SMB twice (which resulted in the Bad_NAME_ERROR), and also attempted transfers twice (which would throw a SMB 36 error). However, once he used the same share name as I did (PhotoSync_CvW), he was able to reproduce the error on his end too. The developer was also very responsive but initially was not able to reproduce the problem on his Synology. He identified that the PhotoSync iOS app seems to be dropping the underscore from the network share name, even if the name was selected from a list of browsable shares in the PhotoSync App menu. was incredibly helpful, walking me through multiple levels of diagnostics to figure out what is going on. Yet I get SMB error bad network name which in the past was a permissions issue. Full permissions for both, recursive file permissions applied to directories and contents alike, etc. So here is my plea: can anyone enjoying PhotoSync and TrueNAS happiness share how they set up their ACL permissions or traditional unix permissions? What does the command line show re: owners/groups? I’m not picky, I just want it to get to work again!įwiw, I set my PhotoSync user to be the owner and the PhotoSyncuser group to be the group owner. I tried using traditional permissions as well as the preferred ACL approach, yet I fail consistently. I know the password login is good since I can browse the network volumes, yet, no transfer can take place. I keep getting errors from PhotoSync as it cannot connect using the same exact credentials as before. That also meant redoing all the shares and that’s where I am currently failing. As part of that process, I nuked my old pool and rebuilt it with a 3-way sVDEV, etc. I have mostly made the transition to TrueNAS and SMB in general.
0 Comments
Leave a Reply. |