Status Update
No update yet.
Comments
ku...@google.com
ku...@google.com
Agreed, you can download photos via the Google Drive API but this hasn't been incorporated into the Photos API yet...
va...@gmail.com
There's already an issue tracking the missing EXIF data here: https://issuetracker.google.com/111228390
Regarding the file at original quality - this is something that's on our list and will be addressed soon, please stay tuned. I'll update this bug once we have an update to share.
Regarding the file at original quality - this is something that's on our list and will be addressed soon, please stay tuned. I'll update this bug once we have an update to share.
va...@gmail.com
We have just released a new version of the Google Photos Library API that supports now this feature.
You can now use the "d" base URL parameter to download the original photo. See the base URL parameter guide for more details:https://developers.google.com/photos/library/guides/access-media-items#image-base-urls
Thanks for your patience!
See our release notes for further detail:https://developers.google.com/photos/library/support/release-notes#2018-07-31
You can now use the "d" base URL parameter to download the original photo. See the base URL parameter guide for more details:
Thanks for your patience!
See our release notes for further detail:
ku...@google.com
I've been testing downloading images using the "d" parameter, but the files returned are not the original files that were uploaded. The release note above reads "d download parameter, to download the original image". The link to the developer documentation doesn't say that the "original" image will be downloaded. Please can you confirm if the d parameter should download the original image that was uploaded to the api, or if this behavior has since changed.
ph...@sprylab.com
I've tested this again, and the file download is a mutated version of the file uploaded to Photos. If I use the web browser and go to photos.google.com , when I "Download" a photo it is byte-for-byte identical to the file I uploaded. If I use the API and attempt to get a copy, with the included "d" base URL, the file is mutated. Both some metadata is missing, as well the photo itself is modified (doing a pixel-for-pixel comparison shows subtle differences).
va...@gmail.com
I can confirm this is still broken and using the 'd' parameter does not return the original photo.
mn...@gmail.com
This is still an issue
so...@gmail.com
How is it marked as fixed? =d parameter still doesn't work
ad...@google.com
ad...@google.com
as...@tunein.com
Hello, Any updates here?
[Deleted User] <[Deleted User]>
I'm not using Dagger but still ran into this issue today. Can't test a fragment with FragmentScenario because my fragment assumes it's inside an AppCompatActivity (to use startSupportActionMode()).
vl...@gmail.com
I need AppCompatActivity for the test as well. Is there any solution here?
al...@gmail.com
Some layouts can't even be inflated using FragmentScenario because of IllegalArgumentException: "The style on this component requires your app theme to be Theme.AppCompat (or a descendant)."
Please prioritize this.
Please prioritize this.
il...@google.com
Re #13 - FragmentScenario already allows you to set a custom theme.
sl...@gmail.com
hello, is there any way to change the fragment attached activity(now it`s an EmptyFragmentActivity), I want to set the activity implements RoboContext. thx~ : )
Description
Support Library.
While FragmentScenario and ActivityScenario are promising to unit test respective components, they don't play well with app based on DaggerFragment and DaggerAppCompatActivity. An instance of application fragment (based on DaggerFragment) is hosted in EmptyFragmentActivity which is not a type of DaggerAppCompatActivity and this makes it not possible to use.
Please add support to provide a custom Activity and Application loaded with mock dependencies to help use FragmentScenario and ActivityScenario for instrumentation tests. Thanks.