An input-only color profile usually implies that is was scanned or captured on a device that embedded an input profile. An input profile is a profile that describes the device in ColorSync language you might say. Photoshop likes to use Working Space color profiles, such as sRGB or AdobeRGB, etc. I would suggest that the file be converted to a working space profile first, then it should be usable in your workflow.
To convert a file to a working space profile, open the file in question, go to the Edit menu and scroll down to "Convert to Profile", choose your favorite space from the top group of working spaces. I would suggest sRGB or AdobeRGB. Save the file and it will be embedded in the file.
Cheers,
Barry Rudick
Aker Imaging
https://community.adobe.com/t5/photoshop/input-only-color-profile-what-in-the-heck-is-that/m-p/7045131
If the file truly has an INPUT ICC profile embedded, then, using the Photoshop's Edit / Convert to Profile and selecting, as destination for the conversion, a working colour space such as Adobe RGB or sRGB would solve that issue.
If you've done that - and still see the error message described earlier, then that seems like a bug.
You can report it as a bug here
https://feedback.photoshop.com/photoshop_family/categories/photoshop_family_photoshop
Also, same limk...
If the file truly has an INPUT ICC profile embedded, then, using the Photoshop's Edit / Convert to Profile and selecting, as destination for the conversion, a working colour space such as Adobe RGB or sRGB would solve that issue.
If you've done that - and still see the error message described earlier, then that seems like a bug.
You can report it as a bug here
https://feedback.photoshop.com/photoshop_family/categories/photoshop_family_photoshop
I hope this helps...
If the file truly has an INPUT ICC profile embedded, then, using the Photoshop's Edit / Convert to Profile and selecting, as destination for the conversion, a working colour space such as Adobe RGB or sRGB would solve that issue.
If you've done that - and still see the error message described earlier, then that seems like a bug.