Skip to content

SDK-325 BCIT Migrate temp domain setup to final custom domain#1050

Draft
joaodordio wants to merge 1 commit intomasterfrom
fix/sdk-325-bcit-domain-migration
Draft

SDK-325 BCIT Migrate temp domain setup to final custom domain#1050
joaodordio wants to merge 1 commit intomasterfrom
fix/sdk-325-bcit-domain-migration

Conversation

@joaodordio
Copy link
Copy Markdown
Member

@joaodordio joaodordio commented May 4, 2026

🔹 Jira Ticket(s) if any

✏️ Description

Migrating the BCIT integration tests off the temporary tsetester.com domain and onto the official engineering-owned bcittesting.com (procured via IT-4410).

What changed

  • integration-tests/src/main/AndroidManifest.xml: the two autoVerify intent filters for App Links now use bcittesting.com and links.bcittesting.com instead of tsetester.com / links.tsetester.com
  • DeepLinkIntegrationTest.kt: TEST_APP_LINK_URL, TEST_BROWSER_LINK_URL and TEST_WRAPPED_LINK_URL constants point at the new domain. The wrapped URL value is stubbed with a TODO_REGENERATE_TOKEN placeholder and a TODO(SDK-325) comment, since the _t/_m/_e tokens are tied to the old Iterable project.

Why the wrapped URL is a placeholder

The wrapped link tokens are project-scoped, so they will only become valid once SDK-36 (the BCIT project migration to the eng org) lands and we can regenerate the link against the new project. I left a loud TODO_REGENERATE_TOKEN so any test run that uses it fails fast with a 404 instead of silently passing or hitting the old project.

Dependencies / sequencing

This PR is intentionally not ready to merge yet. The order is:

  1. Land SDK-36 (new Mobile SDK Testing project)
  2. Land iterable-infra #15167 so links.bcittesting.com resolves and serves AASA / assetlinks
  3. Configure the tracking + destination domain on the new Iterable project, upload AASA / assetlinks. The current Android assetlinks.json on links.tsetester.com is broken (malformed SHA-256 fingerprints, plus the package name does not match com.iterable.integration.tests), so I will regenerate it from scratch with the real signing-key SHA-256
  4. Regenerate the wrapped link, replace the TODO_REGENERATE_TOKEN in this PR, then merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant