The Movie Database Support
Support → API Support
Google Play store rejection
posted by SpringtaleSTAFFMOD on January 18, 2017 at 7:50 AM
I've been trying to get my app deployed into Alpha in the Google Play store.
I've been rejected and was told that:
"Your app will not be reinstated because it violates our Device and Network Abuse"
Split sentence for DaNA link: https://play.google.com/about/privacy-security/device-network-abuse/
"policy by downloading, monetizing, or otherwise accessing YouTube videos in violation of the YouTube Terms of Service or YouTube API Terms of Service. For example, your app curates one or more YouTube videos that contain copyrighted contents not uploaded by the original content owner. Please be reminded our content policies apply to any content to which your app displays or links, including any ads it shows to users and any user-generated content to which it hosts or links."
This is for showing video's attached to a movie. https://developers.themoviedb.org/3/movies/get-movie-videos
When I asked for specific examples, I was told:
"I understand you are using a third party API for your app content. However please note that our content policies apply to any content to which your app displays or links, including any ads it shows to users and any user-generated content to which it hosts or links. Thus I would highly advise you to make modifications to the app to remove any policy violations and prevent further removals.
Some example of the copyrighted content displayed in the app include trailers of Spirited Away or Forrest Gump."
Any thoughts other than to remove the video's entirely?
Reply by Springtale
on July 9, 2017 at 2:04 PM
@travisbell
Has any work been done on the video trailers dealing with the owner / distributor?
Reply by Travis Bell
on July 9, 2017 at 4:39 PM
Not yet.
Reply by Springtale
on July 15, 2017 at 4:35 PM
Do you have a timeframe?
If it's next year, I'll get rid of the videos tab in my app. It doesn't look good if it's empty for 99% of movies.
Reply by Springtale
on February 13, 2018 at 1:11 PM
It's now been over a year. Where is this at?
As I mentioned last year, an easy way to deal with this is to add a JSON element on the video to indicate if it is from the movie owner or a distributor. Leaving the other languages that were created by non-owner/distributors out there may be of service to those who come to the TMDb website, but can't be done by any app iOS/ Google (if they get caught).
For others hitting this problem, this was my experience: https://keithbeattyblog.wordpress.com/2017/11/10/how-long-did-your-app-take-to-get-approved-it-took-my-app/
Reply by Travis Bell
on February 13, 2018 at 1:14 PM
There's some YouTube work that is being discussed as part of a larger studio/network set of features slated for later this year. I would imagine it to be built this year but it's not something that I am working on in the next few months.
Reply by Springtale
on September 10, 2018 at 2:43 PM
@travisbell
I'm curious if there's any update on this issue?
Reply by Travis Bell
on September 10, 2018 at 3:12 PM
There has been no work done on this yet.
Reply by Springtale
on January 23, 2020 at 7:39 PM
@travisbell
I thought I'd check to see if there was any work planned on the Youtube trailer video source status: official / unofficial/ unknown yet?