Transit Android phones and health-department iPhones both use Intelligent Hub, but the log-export taps differ. What should the operator do?
Select an answer to reveal the explanation.
Short Explanation
Hub logs exist on Android and iOS, but the buttons are not twins. Read the official Docs for each platform instead of pretending iTunes works on a transit Android phone.
Full Explanation
When transit Android phones and health-department iPhones both use Intelligent Hub but the log-export taps differ, the operator should follow official Docs for each platform's Intelligent Hub log collection. Platform-specific steps are required rather than assuming one procedure fits both. Cities that run mixed phone fleets for transit and public health avoid blind spots when each OS follows its own supported Hub export method. Assuming only iOS has Hub logs and skipping Android leaves half the fleet undiagnosed. Using the same iTunes file-sharing steps on both platforms is incorrect because Android does not use that path and iOS should prefer documented Hub export. Collecting Horizon Agent logs instead is wrong because they are not a platform-neutral substitute for Intelligent Hub enrollment or Hub app logs. Exam caveat: Cross-platform Hub estates require Docs-driven collection per OS rather than a single folklore procedure. Operational check: Open the Intelligent Hub log-collection documentation for iOS and for Android, export logs from a sample of each fleet, and attach both to the ticket. Keeping the civic evidence trail tied to the failing component also reduces cross-team handoffs that delay public services.