Identify which device hosts the transfer
Open Infuse on the intended iPhone or iPad and inspect Add Files, Browser as the publisher documents. Record the address displayed for that session. The computer is the sending side of this workflow, so a desktop browser window is not evidence that Infuse must be installed on that computer.
Keep this route separate from playing a remote URL or connecting a cloud account. Browser upload moves files into the mobile application for offline use. The address shown by Infuse is a transfer destination; it is not automatically the programme URL to paste into a television streaming player.
Use the displayed address and access choice
Firecore instructs the user to enter the displayed address into a normal browser on the Mac or PC. Once its page loads, the documented Add control or drag-and-drop action begins file transfer. Note whether the failure occurs before the page appears or after a file is selected.
The publisher also offers an Authentication option requiring a username and password for the browser connection. Inspect whether that option is active before treating a login prompt as an unexpected cloud-service sign-in. Do not post the private address or transfer credentials publicly while asking for help.
Verify the receiving copy
After transferring one permitted sample, inspect it inside Infuse on the receiving iOS device and confirm its actual playback. A browser page loading establishes access to the upload interface; a completed transfer and a playable media copy are later results.
For help, provide the receiving platform, Infuse version, computer browser, authentication state and the stage that failed. Keep the displayed address private or redact it. These details distinguish a reversed sender/receiver assumption, an expected transfer-login prompt and a file that reached the device but cannot be played. They also prevent an upload workflow from being confused with streaming an existing network library.