Is this a…:
Standard bug Steps to reproduce this issue:
I frankly am not certain where to report this – it could be a WME bug, it could be an app bug, or it could be user error (although if it is user error, I cannot imagine how it occurs).
Some PURs show new photos for places that are simply black – 100% black pixels, as in the example linked in this report. These are not actual photos at all, as far as I can tell, and I’m not aware of any way to produce this 100% black output using a camera. This example is not unique; I see one of these black photos several times a week, on average, while reviewing PURs in my editing area.
Assuming the users are not intending to submit black images (and these do not all come from the same user account), this appears to be some kind of a bug.
Thank you for your report. I have filed an internal ticket to investigate this issue.
In the meantime, if you come across any other PURs with black photos, please let me know.
This one appears to be absolutely black (I’ve seen some others, which I haven’t reported, that appear all-black but when you turn up the exposure high enough do have some random shaded pixels, which suggests that they are actual photographs taken with the lens blocked somehow).
I have also been getting several blacked out images. Some are even a gradient color, similar to the lens being covered by a hand or on a surface allowing some light to emit onto the image, but with no images containing anything identifiable.
Here is the Permalink for this, which I will attempt to leave open as long as possible for direct diagnostic review, unless it is not needed.
Here is an image that the reporter took, which does not show a completely black image, but one where some light has entered. It gives the appearance that when Waze is communicating with the phone’s camera, there is a delay in taking the captured image, where the user may press the capture button but the capture doesn’t take place until a short time afterward when the user is or has placed the phone down completing blocking an image (camera is already down on a flat surface) or allowing a small amount of light in (camera lens is still in the user’s hand or on a non-flat surface, allowing light to enter the image).
Yes, the PL is correct. Originally submitted by computer. I just checked it now on my phone and it is showing the blacked out image on the PUR. I can check it again on my computer when I get home.
I’ll add an additional note about an oddity that I think might be related to this topic.I guess the issue of black photos hasn’t started to be solved yet. But now we have completely white photos. It’s happening for the second time. It hasn’t happened too many times, but the one before didn’t happen that long ago. It doesn’t seem believable that it’s a coincidence.
Thank you for the example @Max_Booster. I have added it to the internal ticket. I haven’t got any particular updates for now as the issue is still being investigated. I will make sure to keep you posted on the progress.
After clicking the PL, you may need to manually select the designated PUR location, then click on “Review Requests” after the wording stating, “This place has pending update requests.”
Here are some additional PURs with the same issue. I have noticed other editors are deleting the PURs, so as an added measure, I have included screenshots here:
I believe the last one is the most interesting, as it is an image of someone’s legs and feet. This would re-enforce my belief that the app is not grabbing the image at the time the phone’s shutter is activated, but allowing a delay to occur before the camera grabs the image.
If you are interested, I can continue to post additional examples as they come up, but maybe just once a month if that is preferred.
