I'm creating an album at the same time as I upload a new file. I make sure I get the photo ID of the new photo, and then pass than to photosets.create via primary_photo_id.
However, this does not seem to be setting the cover photo for the album automatically. In fact, in the /album/list view, the album shows as a broken "?" image, and the URL to the album thumbnail is .../photo//quad100
If I republish my image via /replace it eventually uses the image as the cover photo, but I'm hoping to solve why it does not work on the initial upload and create of the new photo ID.
I could hack around this by calling photosets.setPrimaryPhoto after I upload the image and create the album, but this REST call is not supported by 23.
Does anyone else see this?
For reference, this is the sequence of events:
1. /upload the photo via POST. See the successful response.
2. Call photos.getInfo on the new ID. Success.
3. Call photos.addTags (unnecessary here, but part of the standard upload so I can rationalize tags that may have changed later.) Success.
4. Call photosets.getList in order to see if I have to create or update an existing album. Success.
5. Call photosets.create with description and primary_photo_id (the same photoID I got, above.) Success.
6. Call photosets.addPhoto to make sure the photo is in the album. I think this is unnecessary on Flickr, but it can't hurt. Success. (If I interrupt the process before doing step 6, I still have the same problem.)
I've checked the response in all cases, and all the IDs I get back are the same as the ones I use in following calls.
When I add another photo to the album I call photosets.getInfo. I can see that the primary photo is the correct photoID of the original photo I uploaded.
[Later]
I guess I can try to use photosets.editPhotos instead of addPhotos when I create the album, and see if that solves the problem. I'll try that.
[Later]
Nope, editPhotos returns success, but the album still doesn't get a cover photo.
