Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vivo Native Tracker #5201

Closed
5 tasks done
nilagangmanok opened this issue Feb 15, 2025 · 2 comments
Closed
5 tasks done

Vivo Native Tracker #5201

nilagangmanok opened this issue Feb 15, 2025 · 2 comments
Assignees
Labels
deny Deny domain(s)

Comments

@nilagangmanok
Copy link

Which blocklist(s) do you use?

Native Tracker

Which category do the domain(s) to be blocked belong to?

Tracking, Analytics/Metrics/Telemetry

Other category

No response

Which domain(s) should be blocked?

asia-vcode-od.vivoglobal.com
in-news-abroad-backstage-interface.vivoglobal.com
in-os-config-appstore.vivoglobal.com
onrt.stsdk.vivoglobal.com
ort.stsdk.vivoglobal.com
pnrt.stsdk.vivoglobal.com
prt.stsdk.vivoglobal.com
tr-domaincfg.vivoglobal.com
tr-romsp-unifyconfig.vivoglobal.com
tr-st-sl.vivoglobal.com
tr-timesync.vivoglobal.com
tr-vcode-api.vivoglobal.com
tr-vcode-od.vivoglobal.com

Which website or app accesses the domain(s)?

Why should these domain(s) be blocked?

Please add the above-mentioned domains in Vivo Native Tracker because these are already included in Pro++.

Confirmation

  • I have verified that no existing issue explains why the domain(s) were previously unblocked or why the blocking request was declined.
  • I have verified that the domain(s) is/are not already blocked.
  • I have verified that the domain(s) is/are active and not inactive (dead).
  • I have provided sufficient details to justify the need for blocking the domain(s).

Terms

  • I confirm that the request does not contain any sexually explicit material or private/sensitive information.
@nilagangmanok nilagangmanok added the deny Deny domain(s) label Feb 15, 2025
@hagezi hagezi added the fixed-pending-release Will be fixed in the next release label Feb 15, 2025
Copy link

Thank you for your support. The issue is scheduled to be fixed in the next release. You will be notified when the issue is finally fixed.

Copy link

This issue has been fixed in release 32025.46.56919

@github-actions github-actions bot removed the fixed-pending-release Will be fixed in the next release label Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deny Deny domain(s)
Projects
None yet
Development

No branches or pull requests

2 participants