After update Android app malfunctioning

  • 1
  • Problem
  • Updated 4 months ago
  • (Edited)
I updated to Covenant Eyes for Android version 3.0.4.43 on Sunday. Since then my CE has been malfunctioning

1) Every time I unlock my Android device, it takes me to the Covenant Eyes app. I keep having to exit out of it. Just this evening it started randomly taking me to it as well.

2) My accountability report was filled with notices that I turned off and on "Device Accountability". I think these coincide with me unlocking my device

3) I used to use WhatsApp no problem. Now when I open it, it says the app is blocked.

I'm using Samsung Galaxy S5 Neo (SM-G903W)
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
  • annoyed

Posted 4 months ago

  • 1
Photo of Syd

Syd, Official Rep

  • 55 Posts
  • 4 Reply Likes
Rafi,
    Thank you for posting in the forum. I am sorry that Covenant Eyes is malfunctioning on your Android device.

1/2) When you updated the Covenant Eyes app on your Android, did you uninstall the existing app then install the updated version? If not, I would suggest uninstalling the app, restarting your phone, and then re-installing.

3) Recently, the Covenant Eyes Rating Team has decided to move the WhatsApp app rating to Highly Mature due to the fact that the app has video chat capabilities. If you desire to have access to this app, please email me at sydney.w@covenanteyes.com so I can provide you with the tools necessary to allow WhatsApp.

I hope this was helpful for you,

Syd
Customer Service Rep.
Covenant Eyes
989-720-8000
M-F 8am-11:45PM EST
Saturday 10am-5:45PM EST
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
Okay I emailed you, thank you. I updated using Google Play. I can't uninstall CE on my phone as it says I'm not authorized to generate an uninstall code. I should be...I'm signed up to CE using WebChaver so I'm guessing that's the issue.
(Edited)
Photo of Syd

Syd, Official Rep

  • 55 Posts
  • 4 Reply Likes
Rafi,
    I emailed you in response.

Syd
Photo of Rafi

Rafi

  • 15 Posts
  • 2 Reply Likes
After updating to 3.0.5.4 the problem was fixed.