Media Picker - Error during content publish: "The selected media is from the wrong folder." Umbraco 15.3.1

Questions
1

“Media Picker” - Error message: “The selected media is from the wrong folder.”

Environment

  • Umbraco version: 15.3.1
  • .NET version: 9.0
  • Database: MSSQL
  • OS: Windows 10

Hello.
I have “Media Picker” field where we have media items. After updating from Umbraco 15.2.3 to 15.3.1, when I try publish content I get error: “The selected media is from the wrong folder.”. Before (in ver 15.2.3) everything was fine. Also in this content page I have two more fields with type “Media Picker” (with different media items) and I also see this error. I found that this issue exist also in another document type with Media Picker.
In one field I can have 10-20 media items, in others only one item.

Has anyone encountered this problem? I would be very grateful for an answer.

The image shows a message saying that "The selected media is from the wrong folder." (Captioned by AI)

image
image765×907 36.9 KB

This screenshot shows the configuration settings for a catalog file picker within a content management system, including accepted file types, media range, start node selection, and image cropping options. (Captioned by AI)
This screenshot shows the configuration settings for a catalog file picker within a content management system, including accepted file types, media range, start node selection, and image cropping options. (Captioned by AI)878×907 37 KB

The image shows a code snippet indicating a validation error with a 400 status code, stating that properties did not pass validation and specifying that the selected media is from the wrong folder in values 3 and 9. (Captioned by AI)
The image shows a code snippet indicating a validation error with a 400 status code, stating that properties did not pass validation and specifying that the selected media is from the wrong folder in values 3 and 9. (Captioned by AI)862×305 18.8 KB

2

Update
Fixed by recreating all broken data types. Сontent inside did not change. Anyway, it looks like this is Umbraco bug/issue