Dor․
Under certain conditions, a change to the scene where one avatar is disabled and another one is enabled may cause the SDK to not propagate an update to the avatar being selected, causing the build process to target the wrong avatar (and fail because it is disabled).
Repro:
  1. 2 avatars in the scene, one with a blueprint attached one without.
  2. Avatar with blueprint attached is enabled, the other one disabled.
  3. Open the SDK panel as a popup window (not docked), select the Builder tab.
  4. Close the SDK panel.
  5. Disable the avatar with the blueprint attached, enable the avatar without a blueprint attached.
  6. Open the SDK panel again, see that the "Avatar Info" still displays details from the avatar with the blueprint, attempting to upload will result an error as the build process will attempt to build the disabled avatar.
This bug is (usually) avoided if the SDK remains open the entire time, or if it is docked (even if it is not in focus).
See attached screenshot for the SDK targeting an avatar that has no blueprint attached, but displays details of a blueprint (fallback eligibility, last updated, version).

Photo Viewer

View photos in a modal