May 18th, 2015
You may notice that at the moment – the apps we have in the store are no longer our popular apps for YouTube celebrities.
You may have also noticed that the versions you already have on your devices are no longer working to play videos…
Don’t worry – we’re working on getting these back to you as soon as possible. YouTube deprecated the version of their public API that we were using that fed our apps with data. In doing so, it caused our current line of apps to stop working.
Rather than allow everyone to download products that simply don’t work, we have temporarily removed them from the app store until we release an updated version. We hope to have that out again in the near future – unfortunately, it is quite an undertaking to rewrite large portions of our apps to read the new data formats, so at the present time we do not have an ETA for when this will be completed.
Thank you for your patience!
April 23rd, 2015
YouTube has changed the way we must access video data. This means that our apps need to fetch video data for your favorite YouTube celebs in a new way, as the previous way has been “disabled”.
You would notice that all of the latest video content is still there, it’s just that the topmost video is not from your favorite content creator.
We are working on a fix and hope to release updates to all of our apps soon – sorry for the interruption in mobile viewing enjoyment.
March 2nd, 2014
YouTube has deployed a fix which has resolved the video playback outage in all of our apps.
Thanks for your patience!
February 28th, 2014
This appears to be a generic YouTube issue. Even web embedded mobile videos OUTSIDE of our apps are not working. We will report the issue to YouTube and hope they resolve it quickly.
Unfortunately, our hands are tied – we apologize for any inconvenience this may be causing.
January 26th, 2014
Several of you have reported that after logging in to use the community features, you started getting errors that say “YouTube has responded with an error”.
After digging in a little we’ve found the issue and we are currently working on the solution. We should have an update soon that fixes this issue. Stay tuned!