IssueTracker

This is the issue tracker for developers using the Google Photos Library API:  http://developers.google.com/photos

For issues with the Google Photos app, please see: https://support.google.com/photos/answer/6156065?hl=en

-----------------------

Before filing an issue, please read and follow these instructions carefully.

First, please search through existing issues to ensure that the bug has not already been reported. You can start the search here: https://issuetracker.google.com/savedsearches/5156057

If the issue has already been reported, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any details of your experience with it.

If your issue has not been reported, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
Video file name sets into YYYY-MM-DD by force. But image file does not.


A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup.

    python3 & requests

        import requests
        url = 'https://photoslibrary.googleapis.com/v1/uploads'
        h = {
            'Content-type': 'application/octet-stream',
            'Authorization': 'Bearer %s' % ACCESS_TOKEN,
            'X-Goog-Upload-File-Name': 'my_video_file_name.webm',
            'X-Goog-Upload-Protocol': 'raw'
        }
        r = requests.post(url, headers=h, data=open('my_video_file_name.webm', 'rb').read())
        upload_token = r.text
        url = 'https://photoslibrary.googleapis.com/v1/mediaItems:batchCreate'
        h = {
            'Content-type': 'application/json',
            'Authorization': 'Bearer %s' % ACCESS_TOKEN,
        }
        j = {'albumId': ALBUM_ID, 'newMediaItems': ['simpleMediaItem': {'uploadToken': upload_token}]}
        r =  requests.post(url, headers=h, json=j)





The calls to the API that lead to the error. Include the sequence of calls, including request headers and body.
Do not include any personal information, authentication secrets, media item or album IDs.

    Uploading bytes response

        X-GUploader-UploadID: UPLOAD_ID
        Content-Type: text/plain
        Content-Length: 531
        Date: Sat, 08 Sep 2018 07:04:11 GMT
        Server: UploadServer
        Alt-Svc: quic=":443"; ma=2592000; v="44,43,39,35"
        UPLOAD_TOKEN


    Creating a media item response

        Content-Type: application/json; charset=UTF-8
        Vary: Origin, X-Origin, Referer
        Content-Encoding: gzip
        Date: Sat, 08 Sep 2018 07:04:17 GMT
        Server: ESF
        Cache-Control: private
        X-XSS-Protection: 1; mode=block
        X-Frame-Options: SAMEORIGIN
        X-Content-Type-Options: nosniff
        Alt-Svc: quic=":443"; ma=2592000; v="44,43,39,35"
        Transfer-Encoding: chunked
        {
            "newMediaItemResults": [
                {
                    "uploadToken": UPLOAD_TOKEN,
                    "status": {
                        "message": "OK"
                    },
                    "mediaItem": {
                        "id": MEDIA_ITEM_ID,
                        "productUrl": PRODUCT_URL,
                        "mimeType": "video/mp4",
                        "mediaMetadata": {
                            "creationTime": "2018-09-08T07:04:13Z",
                            "width": "640",
                            "height": "640"
                        },
                        "filename": "my_video_file_name.webm"  // Actual file name. But it will replace.
                    }
                }
            ]
        }



What steps will reproduce the problem?
1. Upload video file by photos API.
2. Check on web browser or get album contents after a few minutes.


What is the expected output? What do you see instead?  If you see error messages, please provide them.
Uploaded file name and extension.


Please provide any additional information below.
Since Aug 31, 2018.