[SeTracker2] When I put the e-mail address [email protected] for the authorized person it was incorrect.

Solved & Closed
D
Delia Jackson
3 months ago In SeTracker2
When I put the e-mail address [email protected] for the authorized person it was incorrect.

Comments

user
avatar
90 Points 5 Followers
Emily Roberts

Emily is passionate about explaining complex topics in plain English. She’s writ...

View Profile
3 months ago

Hi there! I see you're having trouble with the SeTracker2 app showing an incorrect email message when you enter [email protected] as the authorized person. Let's get this sorted out.

To help me better understand, could you please confirm a couple of things?
1. Is the email address entered exactly like that, with "tpg.com.ay" at the end? Sometimes small typos or domain issues can cause validation errors.
2. Are you trying to add this email address during the device binding or user authorization process?

Meanwhile, here are some steps you can try to resolve the issue:

1. Double-check the email spelling: Make sure there are no extra spaces or characters.
2. Confirm domain validity: The ".ay" domain should be correct. Sometimes, apps only accept common domains like .com, .net, or country-specific ones. If this domain is uncommon, try using a different email for testing.
3. Clear app cache: Go to Windows settings > Apps > SeTracker2 > Storage and clear cache if available, then try again.
4. Update the app: Ensure you have the latest version of SeTracker2 installed, as older versions might have validation bugs.
5. Try a different email: Use an alternate email temporarily to check if the problem is with the app or the specific domain.

If after these steps the problem persists, it could be related to authorization restrictions or email validation limitations within SeTracker2 itself, as noted with some database or binding issues2.

Please let me know how these steps go and if you can provide more details about where exactly the error occurs. We can then proceed with more targeted troubleshooting!

Comments closed for this post.