analyze-unrecognized-apps
Analyze Unrecognized Host Apps
Last run: 2026-09-05 - added 29 return-URL mappings (Happy Coder, Kelivo, Simplenote, Drafts, Uber, Slack, Evernote, LINE, YouTube, eBay, Google Docs, Taobao, Arc Search, plus 5 AASA universal-link fallbacks for Amazon US/UK, ClassDojo, Mercari and Uber Eats) and 11 knownNoSchemeHosts entries. Three mappings (Alibaba enalibaba://, Beeper beeper://, DiDi diditaxi://) went in at explicitly lower confidence and sit under their own comment block. Two lookup techniques worth reusing: the iTunes lookup API (https://itunes.apple.com/lookup?bundleId=...) resolves a bundle ID to an app name and seller URL in one call, and it caught a misidentification - com.codality.NotationalFlow is Simplenote, not the note app the name suggests; and an AASA is not always at /.well-known/ (Hevy serves its own at https://hevy.com/apple-app-site-association). Also note an AASA entry with an empty paths array (DeepSeek) matches nothing and is not a usable fallback. This sample still predates the iOS 26.4 host-resolution fix, so it under-reports.
You are given the following context: $ARGUMENTS
Task
Analyze unrecognized host app bundle IDs from Firebase/Google Analytics and determine which ones need URL scheme mappings added to the app.
Instructions
-
Read the current mappings from
VivaDicta/VivaDictaApp.swift— find theknownURLsdictionary insidereturnURL(forHostId:). TheknownNoSchemeHostsset lives just above it, inattemptReturnToHost(hostId:). -
Get the analytics data — the user will provide a screenshot or list of bundle IDs from the Google Analytics "Unrecognized Host Apps" exploration (see
internal/firebase-analytics-events.mdfor how to access it) -
Cross-reference each bundle ID against
knownURLsandknownNoSchemeHosts, and categorize into: