Fios iPad App Error Code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Recently, maybe within 4-6 weeks ago, I started getting an error code trying to watch specifically the YES Network channel on my Fios TV App and ONLY on the iPad version. The channel works perfectly on my iPhone’s FiosTV App.
The exact error code is 33-PLYB_DRM-1003
It’s connected to the same home WiFi network and the same Fios user account as my phone, and it is the only channel this happens with.
Does anyone know what this code is and how to fix it?
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@MrBok_OG wrote:Recently, maybe within 4-6 weeks ago, I started getting an error code trying to watch specifically the YES Network channel on my Fios TV App and ONLY on the iPad version. The channel works perfectly on my iPhone’s FiosTV App.
The exact error code is 33-PLYB_DRM-1003
It’s connected to the same home WiFi network and the same Fios user account as my phone, and it is the only channel this happens with.
Does anyone know what this code is and how to fix it?
Try un-registering and re-registering the ipad from your system. You could also call the billing department and see if it is an authorization issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@MrBok_OG wrote:Recently, maybe within 4-6 weeks ago, I started getting an error code trying to watch specifically the YES Network channel on my Fios TV App and ONLY on the iPad version. The channel works perfectly on my iPhone’s FiosTV App.
The exact error code is 33-PLYB_DRM-1003
It’s connected to the same home WiFi network and the same Fios user account as my phone, and it is the only channel this happens with.
Does anyone know what this code is and how to fix it?
Try un-registering and re-registering the ipad from your system. You could also call the billing department and see if it is an authorization issue.
