Identify the connection that is missing
Write down whether the source was added as an ordinary network share, a Plex connection or Emby Connect. The same underlying media collection can be reachable through different routes, but the configured connection type determines which sync rule applies.
Firecore says ordinary saved network shares and favourites can sync through iCloud, while Plex and Emby Connect shares require setup on each device because those services use unique device tracking. An absent connection of that type can therefore coexist with other successfully synchronised Infuse settings.
Check the second device’s own access
Use the documented connection process on the second device with the account that is authorised to access the server. Keep that task separate from copying a personal folder favourite. Do not infer server permission from an Infuse purchase or from another household member being signed in elsewhere.
If nothing synchronises, inspect the broader prerequisites instead: current Infuse versions, sync enabled, the same iCloud identity, iCloud Drive and free iCloud storage. The App Store identity can be different. Those checks address a wider failure than the named connection exception.
Distinguish connection state from viewing state
An added server connection and a restored playback position are different results. Firecore lists in-progress playback position, watched history and Up Next among the Pro-only iCloud fields, while ordinary favourites have a broader sync scope. Record the exact missing item rather than describing all of these as the library.
For help, include both devices, Infuse versions, connection type and which settings actually arrived. Avoid deleting the account’s cloud data simply because one excluded connection did not copy. A precise report can show successful general synchronisation alongside a connection that needs its own device setup, or reveal a separate viewing-state question after access has been established.