iOS App doesn't get EXIF info when adding photo via "Camera" (as opposed to Gallery)

MushroomObserver / mo-mobile

Mushroom Observer mobile app

MIT License

0 stars 1 forks source link

iOS App doesn't get EXIF info when adding photo via "Camera" (as opposed to Gallery) #37

Open JoeCohen opened 2 years ago

JoeCohen commented 2 years ago

Differs from the closed issue (since solved) of the app never getting date/time and geoloc from the EXIF header. (IMO a beta version can go out without solving this issue, as there's an obvious, easy work-around.)

The app now does fine when adding photos via the Gallery. But date/time and geoloc are missing when adding photos via Camera. iPhone Xr, iOS 15.3.1, Camera Format Most Compatible. Another data point:

In the App, I Create Observation, Add Photo via Camera.
Then on the iPhone, in Photos, look at the info for the photo. See attached screenshot.
- Saved from Mushroom Observer
- a Date/Time
- "No camera information"

5635

mo-nathan commented 7 months ago

@JoeCohen Are you still seeing this? I'm not on my iPhone.

JoeCohen commented 7 months ago

@mo-nathan I am still having a problem, but I just figured out that I described it incorrectly/imprecisely. What happens is that the photo is saved without gps data if I ask the MO Mobile App to add a photo from Camera. If, on the other hand, I first take a photo with the Camera App, then ask the MO Mobile App to Create an Observation, then add a photo from Gallery, everything works. iphone Xr, iOS 17.3.1.

mo-nathan commented 7 months ago

That sounds more like a problem with Apple Security Theater. I think you have to let iOS know that you're ok with Mushroom Observer using your location or something along those lines.

JoeCohen commented 7 months ago

But:

Location Services, Mushroom Observer, Allow Location Services setting is "While Using the App", which is the most permissive option, and
the Mobile App does know where it's at (Use Current Location, Locate does display the current gps)

You might want to simply close this issue, as I'm the only one who reported it; it may be limited to particular hw, sw, and configuration, and there's an easy work-around for the user.

mo-nathan commented 7 months ago

I finally got a chance to check the correct workflow and I am seeing the same behavior. It's weird because I'm pretty sure I've done that before with no problem.