No, you don't need an HTML page with the app-clip-bundle-id meta tag to fix URL invocation (Notes app or UIApplication.shared.open(url)) for TestFlight App Clips. This meta element is for production web/Safari invocations to trigger the card preview; TestFlight restricts dynamic URL taps/open calls despite green Domain Status and approved swcutil (Site/Fmwk Approval: approved). QR/Local Experience works because it bypasses these limits via explicit developer override. TestFlight Limitations Apple docs confirm TestFlight prioritizes controlled testing: Direct launch from TestFlight app (no card, loads clip). QR/NFC with Local Experience (full card flow). Arbitrary URLs (Notes, other apps) intentionally unsupported to mimic beta safety. Your AASA is perfect appclips entry + /numverify/appclip/* components match, CDN-propagated, swcutil validated. Your Options Method Works for Card+Launch? Setup TestFlight Invocations Partial (testers launch via TF UI) App Store Connect > TestFlight > Build > App Clips > Add Invocation (title + https://www.att.com/numverify/appclip/) Local Xcode Build Yes (full URL flow) Run App Clip target from Xcode; test open URL directly Production Release Yes (complete) Submit for review; add HTML meta at path for web bonus HTML Meta Page No for TestFlight/Notes Only aids browser invocations Recommended next step: Add TestFlight Invocation for testers + use Xcode local build to verify open(url) logic before production. Clear cache if needed (Settings > Developer > App Clips Testing).